Resolve Permission and Workspace Context Issues

Overview

Most “permission” issues in CntX are context problems—not broken accounts:

• You are in the wrong workspace (another brand’s data).
• You are in a delegated client or view-as context with intentional UI restrictions.
• Your role hides admin surfaces (VIEWER, non-admin on Business).
• Subscription status blocks actions after trial expiration.

Understanding company vs workspace vs delegation layers resolves the majority of tickets without support.

When to use

• Expected sidebar items (Billing, Users, Company context) are missing.
• Actions return authorization or role errors.
• Calendar or content belongs to another brand.
• Agency user cannot delete a company or change client billing.

Before you start

• Note your company role (ADMIN, MANAGER, EDITOR, VIEWER).
• Check the Workspace name in the sidebar.
• Look at the browser URL for `delegatedCompanyId`, `ownedCompanyId`, or `adminViewCompanyId` parameters.
• Confirm subscription is active under Settings → Billing when admin screens should appear.

Quick checks

1. Workspace switcher — active workspace matches the brand you intend to edit.
2. Company context — for agencies, Accounts shows whether you are on agency home vs client tenant.
3. Role sufficiency — ADMIN for billing/users; EDITOR minimum for mutating content; VIEWER is read-only.
4. Subscription — trial ended or canceled subscriptions trigger redirects and blocked generation.
5. Delegated vs owned — agencies cannot delete delegated companies; billing may be client-only.
6. Self-edit rules — you cannot change or delete your own role/user record.
7. Browser refresh — stale session after invitation accept or company switch.

Steps

1. Verify workspace isolation

1. Open Workspace in the sidebar.
2. Switch to the correct workspace.
3. Reopen the page that looked wrong (calendar, content, context).

If data now looks correct, the issue was scope—not permissions.

2. Map missing UI to role design

Ask a company ADMIN to adjust your role or workspace assignments if needed.

3. Fix agency and delegation confusion

1. Open `/agency` and confirm which company card you entered.
2. For delegated clients, expect admin editorial access without company deletion or Stripe control.
3. Use Back to accounts before switching to another client—do not bookmark deep links with stale context parameters.

If Home pre-onboarding asks questions “for the client,” you are correctly scoped—answers should reflect the client workspace.

4. Resolve post-invitation access gaps

New invitees who see empty workspaces:

1. Admin reopens Settings → Users → Edit.
2. Assign explicit workspace access and workspace role.
3. Invitee refreshes or re-logs in.

Pending invitations must be Accepted within 48 hours or resent.

5. Handle subscription blocks

If login redirects to pricing:

1. ADMIN opens Customer Portal from Billing (if reachable).
2. Reactivate or upgrade subscription.
3. Non-admins contact their company admin—editors cannot fix billing alone.

6. Escalate true authorization bugs

If role, workspace, and subscription are correct but mutations still fail, email support@cntx.app with:

• User email (not password)
• Company and workspace names
• URL path when error occurred
• Exact error message or screenshot

Expected result

• Correct workspace shows the expected brand data.
• Role-appropriate sidebar renders consistently after refresh.
• Agency users operate client tenants without impossible actions (delete delegated company).
• Reactivated subscriptions restore generation and admin settings.

Tips

• Teach teammates to glance at Workspace before editing calendar items—most cross-brand mistakes happen here.
• VIEWER is useful for leadership review lanes; do not grant it to producers who must edit briefs.
• After accepting an invitation, land on Home and follow Next recommended step to confirm access.
• Ctrl/Cmd-click internal links to compare calendar and settings in parallel tabs without losing context.

Next step

Review the role matrix in Understand Permissions and Delegated Access, or fix publishing-specific errors in Troubleshoot WordPress Publishing.