User permissions reference
This article lists every portal permission in Attik and what it controls: navigation, pages, dashboard widgets, settings menu items, and common in-app actions. Use it when assigning roles, troubleshooting “missing menu” reports, or auditing access.
Written By Ryan Wagner
Last updated 26 days ago
How permissions work
Permissions are set per user under Settings → Users (or applied from a Permission Template).
Each permission has an internal value (used in code) and a label (shown in the Permissions UI).
Category permissions (parent checkboxes) and option permissions (child checkboxes) are separate grants. You often need both the parent and the child for full access to a sub-feature.
Navigation and menus: If a nav item lists several acceptable permissions, the user needs any one of them to see the link.
Individual pages: Opening a URL runs a page-level check. Failing the check sends the user to the unauthorized page even if a parent menu item is visible.
super-admin: Bypasses normal page permission checks (Attik internal / full-access accounts only).settings(category): Grants access to the Settings area in product copy; most Settings submenu items still require their own permission (for examplesettings-users,settings-admin). The Settings gear is available to signed-in users, but each page inside is gated separately.
Dashboard
Category permission: dashboard — Dashboard
Page access: / (Dashboard home) requires dashboard.
Playbook (Scott Home Services Only)
Category permission: playbook — Playbook
Scheduler (internal scheduling)
Category permission: scheduler — Scheduler
Page notes:
/scheduleacceptsscheduler,calendar-office, orcalendar-admin./contactsrequiresscheduler.
Calendar and dispatch
Category permission: calendar — Calendar
Grants: main navigation entry for calendar/dispatch area, Dispatch page access when combined with listed sub-permissions.
Navigation notes:
Calendar nav item shows if the user has any of:
calendar-admin,calendar-office,scheduler,calendar-self,calendar-inspector.Dispatch nav:
calendar-admin,calendar-office,scheduler, orcalendar.Radon Chart nav:
calendar-admin,calendar-office, orscheduler.
Company handbook
Category permission: handbook — Handbook
Tasks and worklists
Category permission: tasks — Tasks
Grants: tasks layout, worklists in navigation context, Tasks menu visibility.
Important distinctions:
Worklists icon in the sidebar uses the
taskscategory permission, but opening/workrequirestasks-checks.Creating/editing custom worklists requires
tasks-admin(not onlytasks-checks).
Human resources
Category permission: human — Human Resources
Page notes:
/hr/payroll/historyacceptshuman-paystubs,human-paystubs-admin, orhuman-payroll./hr/adjustment-managementacceptshuman-payroll,human-payroll-adjustments-office, orhuman-payroll-adjustments-inspector.
Data exports (Reports Hub)
Category permission: data-exports — Data Exports
UI nav label: Reports Hub
Settings
Category permission: settings — Settings
Grants: Settings section (product-level); appears in navigation grants for admins/leaders. Individual menu rows below still need the listed permission(s).
Settings menu quick map (permission required)
Beta features
Category permission: beta — Beta Features
Super admin
Main navigation quick reference
Permission templates and defaults
Permission Templates copy a preset bundle of checkboxes to a user (see Users and staff in Settings).
Default role presets (Inspector, Office, Leader, Exec Leader, Admin) are defined in the product; templates may align with those roles but can be customized per company.
Changing permissions does not automatically update users until an administrator saves the user or applies a template.