Reference An information-oriented lookup resource. Use it to find specific values and definitions.
all access capabilities roles availability atlas
Capability and Access Atlas Look up which customer-facing surfaces depend on role, workspace, or feature availability and how those gates affect page visibility.
Before you start You need to understand why a route, tab, action, or screen is visible for one user and missing for another. Expected outcome Teams can distinguish feature gating, role gating, and workspace mismatch from genuine product failures.
Gate type What it controls Typical examples Role gate Visibility based on workspace role. Activity Feed for admins or owners only. Capability gate Workspace feature availability. AI Assistant, Quotes, Work Orders, Finance subfeatures, Document Templates, and connected-system tooling. Field-work eligibility Whether a member can appear in field assignment flows. Scheduler assignee pickers, field deployments, work-order assignment. Workspace context Which tenant and data boundary the user is currently in. Notifications, assignments, site lists, mobile day run.
Gate type Main tables Why these tables matter Role gate organization_members, organization_invitationsWorkspace role and membership are not inferred from the base users row; they are resolved per organization. Capability gate organization_role_feature_policies, organization_member_feature_overridesThese tables explain why the same role can still see different desk availability in different workspaces or for specific members. Field-work eligibility organization_memberscan_be_scheduled, can_manage_schedule, and scheduler_profile explain assignment visibility and office-vs-field behavior.Workspace context organizations plus nullable organization_id across operational tablesExplains why some records survive outside an org or remain visible after detachment, while CRM and org-admin records do not.
Route or desk Visibility pattern Customers Normal admin desk; later actions may depend on quotes or service-policy availability. Client Handover Admin-only route that requires CRM capability. Scheduling Normal admin desk; scheduler-specific capability and field-work eligibility matter inside the workflow. PPM Forecast Scheduler-capability route for future workload and capacity. Data Quality Admin-only analytics route; CRM and Reports rules are capability-aware inside the dashboard. Workforce Productivity Admin-only analytics route; Work Orders, Scheduler, and Reports badges show source coverage. Quotes Capability-gated in some workspaces. Work Orders Capability-gated in some workspaces. Finance Public customer-facing finance covers receivables and workspace billing; platform-owned credit controls are not part of public docs. Contractors Admin-only route that requires work-order capability; visible UI is submission review, while contractor and grant management are backed by admin APIs. Insights Analytics-style surface that may be limited by workspace feature availability. Reports Core export surface; some related intelligence tooling is platform-only and out of scope here. Document Templates Customer-facing only where template administration is enabled. AI Assistant Capability-gated AI workspace feature. Connected Systems / Integrations / API Keys / Webhooks Availability depends on whether the workspace exposes connected-system operations. Activity Feed Role-gated to office-side admins or owners. Engineers do not get this feed.
Screen or family Visibility pattern Dashboard / Sites / Inspections / Profile Core navigation expected for normal engineer access. Quotes and Work Orders May be available only if the workspace exposes those commercial/remedial workflows. External Job Packs Available to a signed-in app user when an active contractor grant is bound to that user, even if the user is not a member of the sending organization. AI Chat and AI Conversations Capability- or subscription-gated AI feature. Analytics Dashboard Available only where the related analytics feature is enabled. Subscription Visible where upgrade or entitlement handling is relevant to the account. Specialist fire-damper / PDS tools Depend on the job type and system type, not just a static menu decision.
Condition What it changes Member has field work enabled They can appear in scheduler and live assignment pickers. Member is office-only They can coordinate work but should not appear as a field assignee. Work is still draft Engineers should not treat it as live field-ready work. Work is deployed and assigned It can surface in engineer-facing execution views. Work has a valid contractor grant It can surface in contractor portal or native External Job Packs without granting organization membership. Engineer visibility window is set Field visibility is limited to the configured visible-from and visible-until window.
At the data level, this usually means a membership row allows scheduling, a deployment row or deployment-state field marks the work as live, and the underlying inspection or work-order row still points at the same site/system context the engineer will open.
Symptom Likely explanation A route is missing from the admin sidebar Workspace capability or role gate, not necessarily a broken route. An engineer cannot see an assignment Draft state, wrong workspace, wrong assignee, or field-work gate. A contractor cannot see an external job pack Missing or expired grant, revoked grant, inactive contractor, wrong app user binding, or insufficient permission. A customer appointment notification cannot be recorded The job lacks exact date, customer email, or offered/confirmed booking status. AI screens prompt for upgrade or subscription Capability entitlement is not active for that account or workspace. Activity Feed is inaccessible The signed-in account is not an org admin or owner. Quote or work-order shortcuts are absent in mobile The commercial or remedial feature set is not enabled for that workspace.
Confirm the signed-in workspace.
Confirm the user role.
Confirm feature availability for that workspace.
Confirm record state such as draft, deployed, completed, or synced.
Only then treat the missing route or action as a possible defect.