Open app →
Documentation

Organizations, Teams & Members

User guide page covering CompanyOS organizations, teams, members, roles, and invitations

Organizations, teams, and members

An organization (org) is the home for everything in CompanyOS: your projects, tasks, notes, meetings, the activity log, and your people. Every screen in the app lives inside one org, and every org is fully separate from every other one. People you invite see only the org they were invited to. This page covers how to create an org, configure it, invite people, manage roles, and group members into teams.

Where this all lives
Most of what follows happens under Settings, reachable at /app/<your-org>/settings. Settings is organized into tabs: General, Members, Teams, AI, AI Access, Vocabulary, Templates, Workflow, and Automations. This page focuses on General, Members, and Teams.

Creating an organization

When you first sign in, CompanyOS sends you to a workspace picker that lists every org you belong to. If you have exactly one org, it takes you straight in. If you have none, it prompts you to create your first one.

  1. Open the workspace picker
    Go to the app. If you are not auto-redirected into an org, you will land on the "Choose a workspace" screen that lists your organizations.
  2. Click "New organization"
    Use the button in the header of the organizations card. If you have no orgs yet, the empty state shows a "Create organization" button instead with the same effect.
  3. Name it
    Enter a name such as "Acme Inc". The name must be at least 2 characters. There is no separate description field at creation time; you can add a description later via the API, and rename anytime in Settings.
  4. Click "Create"
    CompanyOS creates the org and drops you straight into your first project so you can start working immediately.
You become the owner automatically
Whoever creates an org is made its owner. CompanyOS also seeds a default task workflow (the set of statuses your tasks move through) for the new org so you can start creating tasks right away.

About the slug

Every org gets a URL-friendly slug derived from its name (for example, "Acme Inc" becomes acme-inc). The slug is unique across all of CompanyOS. If your chosen name produces a slug that is already taken, a short random suffix is added automatically (for example, acme-inc-4f9a2c). The slug is stable: renaming your org does not change it.

Organization settings (General)

The General tab under Settings is where you manage the org's core identity. The main card lets you rename the organization.

  1. Open Settings → General
    Navigate to Settings and stay on the default General tab.
  2. Edit the name
    Change the value in the Name field. The Slug field below it is shown but disabled, because the slug never changes after creation.
  3. Save changes
    Click "Save changes". The button stays disabled until your new name is at least 2 characters and actually different from the current name.

The General tab also surfaces two related panels: Deleted projects (where you can review and restore projects that were removed) and Project notifications (where you tune which project events notify you). Renaming the org is recorded in the activity log.

Renaming is an admin action
Editing the organization requires admin or owner role. A plain member who opens General will be able to view it but the save will be rejected by the server.

Members and roles

Everyone with access to an org is a member of it, and every member holds exactly one of three roles. The roles are a strict hierarchy: an owner outranks an admin, who outranks a member.

RoleRankIn one line
OwnerHighestFull control, including managing other owners and the org's existence.
AdminMiddleDay-to-day management: people, teams, projects, invites, settings.
MemberBaseDoes the work: projects, tasks, notes, meetings. No management powers.

What each role can do

CompanyOS enforces roles on the server, so these limits hold no matter what the UI shows. The key dividing line is that managing the org (people, teams, invites, projects, org settings) requires admin or higher, while a few sensitive actions are reserved for owners only.

ActionMemberAdminOwner
Use the org: view and work on projects, tasks, notes, meetingsYesYesYes
See the members list and teamsYesYesYes
Rename the organization / edit settingsNoYesYes
Invite people (as member or admin)NoYesYes
Revoke a pending inviteNoYesYes
Change a member's role (member ↔ admin)NoYesYes
Remove a memberNoYesYes
Create, rename, and delete teams; manage team membershipNoYesYes
Create, archive, and manage projectsNoYesYes
Invite someone as owner, or grant/change an owner roleNoNoYes
Remove an existing ownerNoNoYes
Owner is a superset of admin
Anything an admin can do, an owner can do too. The owner-only rows above are the extra powers that admins do not have: everything to do with creating or touching other owners.

Viewing the members list

Open Settings → Members. The Members card lists everyone in the org with their name, email, and role, in the order they joined. Your own row is marked with "(you)".

If you are an admin or owner, each row shows a role dropdown and a remove button so you can manage people inline. If you are a plain member, you see the same list but roles appear as read-only badges and there are no management controls.

Changing a member's role

  1. Open Settings → Members
    You must be an admin or owner to see the role controls.
  2. Find the person
    Locate their row in the Members list.
  3. Pick a new role
    Use the role dropdown on their row and choose owner, admin, or member. The change saves immediately.

There are guardrails to keep the org safe:

  • You cannot change your own role. This prevents an admin from accidentally self-promoting and prevents an owner from self-demoting out of control.
  • Only an owner can grant, modify, or remove an owner role. An admin can move people between member and admin, but cannot touch anyone who is (or is becoming) an owner.
  • The last owner cannot be demoted. If there is only one owner left, the system refuses to lower their role, so an org always has at least one owner.

Removing a member

  1. Open Settings → Members
    Admin or owner only.
  2. Click the remove (trash) button
    It sits at the end of the person's row. Your own row's remove button is disabled, so you cannot remove yourself this way.
  3. Confirm
    The member loses access to the org immediately.
Removal also clears their team and project memberships
When you remove someone from the org, CompanyOS also strips them out of every team and every project they belonged to within that org, in the same step, so nothing is left pointing at a person who no longer has access. The same owner protections apply: only an owner can remove an owner, and the last owner cannot be removed.

Inviting people by email

You add people to an org by inviting them by email. They do not need a CompanyOS account yet. When they accept (after signing in or signing up with that same email), they become members.

Sending an invite

  1. Open Settings → Members
    The "Invite people" card appears only if you are an admin or owner.
  2. Enter their email
    Type the address you want to invite, for example teammate@company.com.
  3. Choose a role
    Pick the role they will join as. The dropdown offers member or admin. To invite someone directly as an owner, you must be an owner yourself (see note below).
  4. Click "Invite"
    CompanyOS creates the invitation and shows you a copyable invite link.
  5. Share the link
    Click the copy icon to grab the invite URL and send it to the person however you like. The link is the fastest way to get them in.
The invite link is shown once
The one-time invite token is only returned at the moment you create the invite, which is why the copyable link appears right after you click Invite. The token itself is never stored in readable form, so if you lose the link, revoke the invite and send a fresh one rather than trying to recover it.

A few rules apply when creating invites:

  • Default role is member if you do not pick one.
  • One pending invite per email per org. If there is already an unaccepted invite for that address, you cannot create a second one. Revoke the first if you need to change the role.
  • No inviting existing members. If the email already belongs to a member of this org, the invite is rejected.
  • Invites expire after 7 days. After that the link no longer works and you will need to send a new one.
  • Owner invites are owner-only. Only an owner can invite someone as an owner; an admin attempting it is blocked.

Pending invites and revoking

Below the invite form, the "Invite people" card lists every pending invite with its email and role. Each one has a trash button. Click it to revoke an invite you no longer want; the link immediately stops working. Only invites that are still pending can be revoked (an already-accepted or expired one cannot).

Accepting an invite

When you receive an invite link, it points to a page that joins you to the organization. You must be signed in with the same email the invite was sent to.

  1. Open the invite link
    It takes you to an "Accept your invite" page.
  2. Sign in or sign up with the invited email
    If you are not signed in, use the "Sign in" or "create one" links on that page. The account must use the exact email the invite was issued to, otherwise the server rejects it.
  3. Click "Accept invite"
    CompanyOS adds you to the organization and takes you straight to its projects.

If acceptance fails, the page tells you the invite could not be accepted: it may have expired, already been used, or been issued to a different account. In that case, ask an admin or owner to send a new one. Common reasons an accept is refused:

  • Wrong account. The invite was issued to a different email than the one you are signed in with.
  • Expired. More than 7 days have passed; the invite is marked expired on the spot.
  • Already used or revoked. The invite is no longer pending.
  • Already a member. You are already in that org, so there is nothing to accept.
Elevated invites are re-checked at accept time
If you were invited as an admin or owner, CompanyOS double-checks the inviter's standing at the moment you accept. If the person who invited you has since been demoted or removed and no longer holds that level of authority, the elevated grant is rejected as stale. This keeps demoted or departed staff from leaving behind invites that would hand out power they no longer have.

Teams

A team is a named group of members inside an org, used to organize ownership: teams own projects. Teams are lightweight: a team has a name and an optional description, and a set of members drawn from the org. The same person can be on more than one team.

Creating and editing teams

  1. Open Settings → Teams
    The create form and the per-team controls appear only if you are an admin or owner. Members see the team list read-only.
  2. Create a team
    Type a name (for example "Platform", at least 2 characters) in the "New team name" field and click "Add team". Team names must be unique within the org.
  3. Rename a team
    Click the pencil icon on a team row, edit the name inline, and click the check to save (or the X to cancel).
  4. Delete a team
    Click the trash icon on the team row and confirm in the dialog.
Deleting a team is permanent
Deleting a team cannot be undone. Any projects owned by that team lose their team assignment (the projects themselves are not deleted). The team's members simply stop being on that team; they keep their org membership.

Team membership

You can only add someone to a team if they are already a member of the org. CompanyOS rejects adding a non-member, and it will not add the same person to a team twice. Managing team membership (adding and removing people) is an admin-or-owner action, like the rest of team management. When you remove someone from the whole org, they are taken off all their teams automatically.

Quick reference: who can manage what

If you ever wonder why a button is missing or an action is refused, it comes down to your role. Management surfaces (invite people, change roles, remove members, create or edit teams, manage projects, edit org settings) require admin or owner. The handful of owner-only actions all concern other owners: inviting as owner, granting or changing an owner role, and removing an owner. Everything else, the actual work in projects, tasks, notes, and meetings, is open to every member.