Troubleshooting Applications Access
Applications uses two access layers. The first controls whether you can browse the Applications explorer. The second filters the workspaces, applications, pages, and actions available inside it. Most unavailable resources are hidden rather than shown as locked cards.
Before you start
- Open the canonical
/applicationsroute onhttps://<workspace>.raptix.app. - Clear the search field before concluding that an item is unavailable.
- Record the exact workspace, application, page, and action you need.
- If the page says Couldn't load Applications, follow the connection guide instead.
Access restricted replaces the workspace explorer
What you see: The Applications shell opens, but the content area shows Access restricted and You do not have permission to view workspaces.
What it means: Your account can reach the shared Applications shell through another capability, but it does not have the Applications explorer access needed to browse workspaces.
Member action: Ask an administrator for Applications access. Include the workspace or application you ultimately need so the administrator can also create the correct resource grant.
Administrator check: Confirm that the user's effective role includes Applications access, then review their Applications grants. Do not solve this by sharing another account or an authenticated link.
Applications loads but no workspaces appear
What you see: The normal Applications header is visible, but the content says No workspaces found or No workspaces available.
What it can mean:
- The current search does not match an available workspace.
- The user has Applications explorer access but no View grant that exposes a workspace, application, or page.
- The organization has no available workspace content for this account.
Member action: Clear search. If the list remains empty, ask for View access to the required resource.
Administrator check: Review the user's direct and role-based grants. A grant to an application or page should expose its parent path for navigation; the user does not need an unrestricted global grant merely to reach one item.
A workspace, application, or page is missing
RAPTIX does not draw placeholders for resources the user cannot view. Match the missing item to the narrowest useful request:
| Missing item | Request | Administrator check |
|---|---|---|
| Workspace | View access to the workspace, or to a child resource within it | Workspace and child grants |
| Application inside a visible workspace | View access to that application, or to a page within it | Application and page grants |
| Page inside a visible application | View access to that page | Page grant and parent mapping |
| Runnable workflow form | Access to the form's application plus an active, published form | Workflow publication, scope, and access |
A parent-level View grant expands to its children. A page-level grant should expose only the parent path required to reach that page, not every sibling page.
An action is missing
Applications actions are independently gated. Seeing a resource does not imply you can perform every action on it.
| Missing action | Common reason |
|---|---|
| Edit on an App Builder page | No effective Edit grant, non-Enterprise plan, or no edit address for that page |
| Edit on a runnable workflow | No Edit grant covering that workflow's scope |
| App Builder | Non-Enterprise plan, App Builder feature access is off, or no applicable builder-opening grant |
| Flow Builder | Flow Builder access is not assigned |
| Workflow | Workflow dashboard access is not assigned |
| Documents | Documents access is not assigned |
| New | Creation access is not assigned, or the current hierarchy level does not support creation |
| More | Applications administrative actions are not assigned |
| Rename or delete icons | The workspace or application is not user-manageable, or the current account is not its manager |
Request the specific capability required for the task. Avoid asking for administrator or global access when a scoped grant is sufficient.
Shared and Private labels do not replace RAPTIX grants
An App Builder application card can show Shared or Private. This is application metadata, not a promise that every RAPTIX user can browse or edit the application. RAPTIX still applies the user's explorer and resource grants before showing workspaces, applications, and pages.
Runnable forms have their own Public or Private setting. That setting controls the form link; editing and catalogue visibility remain separate capabilities.
After access changes
- Return to
/applicationsor reload the Applications tab. - Clear any search text.
- Navigate from Workspaces to the target item again.
- If a role assignment changed but the old state remains, sign out and sign back in to refresh the session.
- If the item is still unavailable, ask the administrator to verify the saved grant, principal, scope, and capability rather than creating duplicate grants blindly.
Frequently asked questions
Why can I see a parent but not all of its children?
A child grant exposes enough parent hierarchy for navigation without granting sibling resources. This is expected for least-privilege access.
Why did Edit disappear after it worked before?
Your Edit grant, plan entitlement, page edit address, or role assignment may have changed. Ask an administrator to check all four rather than only View access.
Why can I open Workflow inside Applications but not Workspaces?
Workflow and the Applications explorer are separate capabilities within the shared shell. Request Applications explorer access if you also need the workspace hierarchy.
Can an administrator send me their page URL?
They can send a canonical resource location, but RAPTIX still evaluates your own session and grants. Never reuse someone else's authenticated URL or account.