Profile permissions and states

Profiles combines organization membership with authorization on each company, person, or fund profile.

Access layers

Access	Browse lists	Open profile	Edit profile	Manage collaborators
Organization member without a collaborator role	Yes	No	No	No
Viewer	Yes	Yes	No	No
Editor	Yes	Yes	Supported inline company-profile fields	No
Full access	Yes	Yes	Yes	Yes
Organization or global administrator	Yes	Yes	Yes	Yes

Organization administrators bypass profile-level collaborator checks. A normal member still needs Viewer-or-higher access to open a record after finding it in a list.

The role chooser describes Editor as able to edit profile content. Current route enforcement is narrower: inline company-profile fields accept Editor-or-higher changes, while dedicated company, person, and fund Edit routes require Full access. Fund intelligence and every Manage access route also require Full access or administrator access.

Collaborator safeguards

• A newly created profile gives its creator Full access.
• Full access can add collaborators, change roles, and remove collaborators.
• Profiles must retain at least one full-access collaborator.
• The last full-access user cannot downgrade their own role or remove the last full-access collaborator.
• A collaborator must be a member of the same organization.

Administrator-only areas

Organization administrators can open Profile reviews, Signal triage, Taxonomy, Custom fields, and Relationships. Ordinary members do not receive these navigation items or routes.

Profile states

State	Meaning
Draft	The profile is being prepared.
Published	The profile is in its published lifecycle state.
Archived	The profile is retained but no longer active.
Discarded	The profile has been set aside.

State does not grant access. Draft, Published, Archived, and Discarded records still use organization and collaborator authorization.

Profile reviews use a separate lifecycle: Pending, Approved, or Rejected. Review decisions are available only on the administrator review routes.

Access failures

Profiles uses You are not authorized to access this page when the signed-in user lacks the route’s required access. Profile not found means the requested record was not found in the route’s organization scope.