Portal Access Control¶
Each portal decides who can view it, who can edit it and who can manage it. Use this to send the finance dashboard only to the finance team and the operations dashboard only to operations, while keeping editing to the people who build them.
How access is decided¶
A user's access to a portal is resolved in this order:
- A setting for the user on the portal, if there is one.
- Otherwise, a setting for the user's role on the portal.
- Otherwise, if the portal has Inherit access from workspace turned on, the role's Portals permission.
- Otherwise, no access.
Viewing a portal does not need the Data Sources permission. Data read from an external database still needs access to that database connection, as it does for reports.
Only members of the portal's workspace can open it. A setting on a portal never lets in someone from outside the workspace — not even through the published link.
| Access Level | What the user can do |
|---|---|
| No Access | The portal is hidden from the portal list and cannot be opened. Its links show "not found". |
| Read | Open the portal in preview and through its published link, with its data. Opening it from the portal list shows the preview instead of the designer. |
| Write | Edit the portal in the designer, publish it and duplicate it. |
| Full Access | Delete the portal and configure its access. |
New portals¶
A new portal starts with the same access as a new report:
- Inherit access from workspace is on, so everyone gets their role's Portals permission.
- The user who created it has Full Access.
Duplicated and imported portals start the same way, with the user who duplicated or imported them as the one with Full Access.
Configuring access¶
- Open the Portals app and select a portal in the list.
- Click Configure access (also available from the right-click menu). This requires Full Access to the portal.
- Add users and roles and set an access level for each.
- Turn Inherit access from workspace off to limit the portal to only the users and roles listed.
- Click Save.
Designs and themes¶
Designs and themes are shared by many portals, so they are not controlled per portal. Access to them comes from the role's Portal Designs and Portal Themes permissions. Creating a portal requires at least Read on Portal Designs, because every portal is built on a design.
Shared parts of a page that belong to its design — such as headers, footers and navigation — follow the Portal Designs permission, not the portal's own access settings.