Organization Roles
Understand the three organization-level roles in Cogram (Owner, Admin, and Member) and what each role can do.
Last updated
Was this helpful?
Understand the three organization-level roles in Cogram (Owner, Admin, and Member) and what each role can do.
Every user in a Cogram organization has one of three organization-level roles: Owner, Admin, or Member. These roles control what a user can do across the entire organization, including creating and managing projects.
Organization roles are separate from Project Roles, which control what a user can do within a specific project.
Access and view their own projects
✓
✓
✓
Create new projects
✓
✓
✓ ¹
View any project in the organization
✓
✓
Update settings on any project
✓
✓
Archive or delete their own projects
✓
✓
✓ ¹
Delete any project
✓
✓
Create, edit, or delete project types
✓
✓
Invite and remove organization members
✓
✓
Manage SSO, billing, and integrations
✓
✓
Assign and remove the Admin role
✓
¹ Members can create, archive, and delete their own projects by default. An org Admin or Owner can restrict these actions to Admins and Owners only. See Project Management Permissions.
Full control over the organization. Owners can manage all projects, invite or remove members, configure integrations, and assign or revoke Admin roles. There is typically one Owner per organization.
Organization-wide administrator. Admins can create, update, and delete any project in the organization, even projects they are not a member of. Admins can also invite members and manage organization settings, but cannot assign or revoke Admin roles. This role is suited for project managers or operations leads who need to oversee the full project portfolio.
Standard organization user. Members can create new projects and access any project they have been added to. They cannot view, modify, or delete projects they have not been invited to, and have no access to organization administration settings. An org Admin or Owner can optionally restrict project creation, archiving, and deletion to Admins and Owners only.
When an Owner or Admin accesses a project, they have full administrative rights over that project regardless of whether they have been explicitly added as a project member. This allows Owners and Admins to manage the project portfolio without needing to be listed on every project.
For Members, access to a project's content is governed entirely by their Project Role (Owner, Lead, Member, or Viewer) within that project.
Groups let you organize users by team, department, or office location and assign project access in bulk. See Groups for full details on creating groups, managing membership, and how group-based project access works.
The Group Admin badge is a per-group capability, not an organization role. It can be granted to any user in the organization (including Members, Admins, and Owners) and the user keeps their existing org role. A Group Admin can manage members and settings for the specific groups they administer, but has no organization-wide authority. See Group Admin Role for details.
Organization roles are managed in Organization Settings > Users. Only Owners can assign or remove the Admin role.
Last updated
Was this helpful?
Was this helpful?