Skip to main content

Roles & Permissions

Celeredge controls access at two levels: your organization role (firm-wide) and your engagement membership (per piece of work). This page is the detailed reference; for the plain-language version see User Roles.

The two levels

  • Organization role decides firm-wide capabilities: seeing the CRM, administering people, practices, integrations, and billing.
  • Engagement membership decides what you can see and do inside a specific engagement, independent of firm role. Being on the engagement team is what grants access to its evidence, assessments, and deliverables.

Organization capability matrix

CapabilityMember (Consultant)ReviewerExternalOrg Admin
See firm pipeline (Prospects/Accounts/Engagements)✅ (read)Limited
Work inside engagements they're onViewLimited
Create engagements
Invite users / assign roles
Manage practice visibility & Practice Leads
Configure integrations
Manage settings & billing
Author/publish frameworks(Celeredge staff only)

Even Org Admins do not author frameworks. Framework authoring and publishing is restricted to Celeredge platform staff — see Platform Administration.

Engagement roles

Within an engagement, members are added with an engagement-level role (e.g. consultant), and one person is the engagement lead. Engagement membership is the gate for:

Practice Leads

A Practice Lead is a Member additionally assigned to own a practice. This is a responsibility (methodology ownership), assigned by an Org Admin — see Practice Leads.

Programmatic access (API keys)

Celeredge supports API-key access for programmatic use, presented as X-API-Key: id#key. Keys are scoped (e.g. to a user or an agent). See the API Reference.

Best practices

  • Least privilege. Grant the narrowest role that lets someone do their job.
  • Engagement membership over broad roles. Use team membership to scope access to client work, rather than elevating firm roles.
  • Review periodically. Audit who has Org Admin and who's on sensitive engagements.