---
seo:
  title: "Access Control"
  description: "How to control access to navigation items and pages based on user authentication status."
llm_context: "The portal offers granular control to selectively show or hide content based on whether the viewer is currently logged in, and the set of roles their firm has been granted."
category: "guide"
related:
  - "/portal/reference/navigation"
  - "/portal/guides/organisation"
---

## Access Control

When companies first consider moving from legacy PDFs to a web-based portal, authentication and security are usually the first things they want to talk about. They need to be sure only the _right_ people can see their content, and that those people are always looking at the latest version.

:::tip PDFs give a false sense of control
Sending a targeted PDF to an individual feels safe — it's easy to assume that keeps it out of a competitor's hands. In reality, control ends the moment you hit send. You have no way of knowing whether the recipient stores it on a shared drive, attaches it to a JIRA ticket, or forwards it on internally. Once that happens, you've lost visibility over who's reading your documentation, and why.
:::

The portal is designed to flexibly accommodate a wide variety of authentication and role-based access control requirements.

### Types of Access Control

The portal provides the following types of access control, which can be used in any combination:

1. **Global Authentication**: Fully hides the portal from unauthenticated users; they hit a login page before seeing any landing page.
2. **Page-Level Authentication**: Controls access to individual sections and pages within the site. A self-service conformance site, for example, might restrict real-time log visibility to authenticated users while leaving the rest of the site open.
3. **Role-Based Access**: Restricts access to sections or pages based on the role or services granted at the firm level — for example, restricting information by asset class.
4. **On-Page Visibility**: Fine-grained control to hide or show specific _sections_ within a given page based on authentication status and/or roles.

See the [Access Control Reference](/portal/reference/access) for the technical details on configuring each of these.

### Setting Firm Roles

Admin users can assign one or more roles to customers (or "Entities") via the Admin Dashboard. All declared users within that firm then inherit these roles, which control access to various sections of the portal.

Roles are simply lightweight strings, which can be added or removed instantly.

![Figure: Role assignment in the admin dashboard.](https://docs.fixspec.com/api/docs/image/portal_role_admin.png)

### FAQs

:::faqs
::faq[Can a single user belong to more than one role?]{#faq_access_multiple_roles_per_entity}
Yes — a firm can be assigned one or more roles, and every user within that firm inherits all of them.
::
::faq[Can I combine the different types of access control on the same page?]{#faq_access_multiple_roles_per_page}
Yes, that's the point — Page-Level, Role-Based and On-Page Visibility controls can all be applied together, so you can, for example, show a page to authenticated users generally but hide one section from everyone except a specific role.
::
::faq[How quickly do role changes take effect?]{#faq_access_role_change_delay}
Roles can be added or removed instantly by an admin via the dashboard — see [Setting Firm Roles](#setting-firm-roles) above.
::
::faq[Do non-readable assets obey these access restrictions?]{#faq_access_sitemap_llms}
The portal platform will auto-generate certain assets for your site aimed at assisting search engine crawlers and LLMs to understand it. These files include `robots.txt`, `sitemap.xml` and `llms.txt` files.
All of these assets are automatically generated for you, and are designed to obey the visibility rules. **Only content which is available to unauthenticated, non-role users will feature in these files**. Importantly, this means that sites which are set for global authentication (i.e everything is behind a logon screen), then NOTHING will be available to search engines or LLMs.  
::
:::
