When you build a custom access policy that includes Portals, you can grant the actions listed here. Portals groups them into administrator actions, day-to-day actions, page and menu permission families, and query and report access.
Permission Action Groups
Use the groups below to find the actions someone needs for their Portals work. Administrator actions require an administrator-level policy; read-only and day-to-day policies do not include them.
Administrator Actions
Only an administrator-level policy grants these actions. A read-only or day-to-day policy does not include them.
| Action | What it controls |
|---|---|
| Reach the Portals setup area | Opens the Setup section in the Portals Console |
| Run Portals maintenance | Opens the Maintenance screen, including the option to rebuild a site's map |
| Run Portals maintenance | Opens the Maintenance screen, including the option to rebuild a site's map |
Day-To-Day Actions
Use these actions for the content work staff usually do in Portals.
| Action | What it controls |
|---|---|
| Edit site settings | Lets someone change a site's settings, including header and footer markup, scripts, and stylesheets |
| Design assets | Lets someone work with assets and the design playground |
| Install features | Lets someone install a portal feature into a site |
| Access installed features | Lets someone view which features are installed on a site |
| Remove features | Appears in the permission list, but has no effect because there is currently no way to uninstall a feature from a site |
| Edit site settings | Lets someone change a site's settings, including header and footer markup, scripts, and stylesheets | | Design assets | Lets someone work with assets and the design playground | | Install features | Lets someone install a portal feature into a site | | Access installed features | Lets someone view which features are installed on a site | | Remove features | Appears in the permission list, but has no effect because there is currently no way to uninstall a feature from a site |
Page and Menu Permissions
Pages and menus use permission families instead of the individual actions listed in the other sections. Grant the page or menu family through a policy when someone needs to open, create, or edit pages or menus in the Console.
| Family | What it covers |
|---|---|
| Page actions | Opening, creating, and editing pages |
| Menu actions | Opening, creating, and editing menus |
Query and Report Access
Portals includes two actions for Portals queries and reports, but those actions do not currently restrict access.
| Action | What it controls |
|---|---|
| Access Portals queries | Appears in the permission list, but there is currently no Portals query surface for it to control |
| Access Portals reports | Appears in the permission list, but the Reports and Dashboards page does not currently check it |
Warning
Both query and report actions appear in the permission list, but neither currently restricts anything in the product. Do not rely on withholding either one to keep someone out of reports.
| Access Portals queries | Appears in the permission list, but there is currently no Portals query surface for it to control | | Access Portals reports | Appears in the permission list, but the Reports and Dashboards page does not currently check it |
Warning
Both query and report actions exist in the permission list, but neither currently restricts anything in the product. Do not rely on withholding either one to keep someone out of reports.
Related
See also Portals Access Policies, listed under this application's other articles.