What is Stacks?
Stacks is a web-based content management system (CMS) that provides everything you need to create and manage your digital research experience. The platform is designed to be user-friendly and intuitive so users with all experience levels can manage the site independently without needing external support or assistance.
How do I access my Stacks site?
To access your Stacks site, begin by either typing or pasting the provided URL into your web browser.
Logging in to Stacks
There are two different types of user accounts that can log into your Stacks site.
- Patrons, (sometimes also referred to as users) are typically individuals who are required to log in to access content on your site. Patrons have no level of administration access
- Staff users, are the individuals that log into your site and have some form of administrative role for the purpose of creating and managing content on your site. There are various "staff user" roles that provided different levels of access for creating and managing content depending on your needs
To login into Stacks
Staff users
- On the homepage, scroll to the very bottom of the page and click the Staff login link in the footer; OR
- Click the Log In link in the top right corner of the Stacks site
- In the window that opens, click the Go to Staff Login link
Patrons/Users
- Click the Log In link in the top right corner of the Stacks site
- If your organization has enabled single sign on (SSO), you may see an option to login via the SSO provider
Once logged in, and depending on your site configuration, individuals may be directed to the Homepage, My Account page, the Dashboard (for staff users only), or another page.
Can anyone access my site?
At first yes, unless otherwise configured by your IPM or LSE, your Stacks site can be accessible by anyone that has the URL. With that being said, and again, unless otherwise configured by your IPM, LSE, or AE, your site will initially be a blank slate with no content added yet.
Can I restrict access to my site or its content?
Yes, if needed, during a trial, during implementation, or after you site is launched, site-wide password protection can be enabled to force users to log in to access the site as a whole.
Alternatively, you can also make most of your site accessible to anyone while still forcing them to login to access certain types of content (like catalogs or other resources). Other forms of content protection can also be enabled, including:
- By patron segment
- By role
- IP whitelisting