Organization, teams and members
Manage your organization, its teams, its members and its plan.
Your organization holds teams, teams hold people and components, and the plan sets how many of each you get. All of it lives under Settings, in the Administration group.
For an organization owner or an admin of the Core team.
Organization
Settings → Organization holds the organization itself.
Under General you can change the organization's Logo, Name and URL.
Two switches sit below it:
- Share AI usage data — whether Compfeed may use your AI usage to improve the product. You choose this during onboarding and can change it here at any time.
- Allow MCP server — whether AI coding tools may reach this organization. Owners only. See MCP.
Teams
Settings → Teams lists your teams and is where you add more.
A team owns its own processes and its own components. People are added per team, with a role per team, so somebody can be an editor on one team and a viewer on another.
The Core team
Compfeed creates a team called Core when you set up the organization, described as your central component library.
Core carries more weight than its components suggest: an admin of the Core team holds the organization-level admin powers. If you want somebody to administer the organization without making them its owner, make them an admin of Core.
Members
Settings → Members is where you invite people and manage who is in the organization.
Invite somebody by email address and give them a role on a team. They get an invitation to accept.
Roles
There are two role scopes. Everyone has one organization role, and one role per team they belong to.
| Role | Scope | Can do | Uses a paid seat |
|---|---|---|---|
| Owner | Organization | Everything, including billing, ownership and Allow MCP server | Depends on their team roles |
| Member | Organization | Whatever their team roles allow | Depends on their team roles |
| Admin | Team | Create and change processes, including published ones. Add, edit and delete components. Manage the team | Yes |
| Editor | Team | Create processes and edit them while they are drafts. Add, edit and delete components. Suggest Manifest changes | Yes |
| Viewer | Team | Read processes, components and Manifests | No |
Only a team Admin can change a process after it has been published. An Editor can create one and edit it as a draft.
Seats
A paid seat is used by anyone holding Admin or Editor on at least one team. Viewer is free.
One person is one seat, however many teams they are an admin or editor of. So adding somebody to a second team as an editor costs nothing extra, while promoting a viewer to editor uses a seat.
This is why it is worth giving read-only people the Viewer role rather than Editor by default.
The usage panel in the settings sidebar shows where you stand: Teams, Members, Admin/Editor seats, Components and AI credits per month.
Billing
Settings → Billing shows your plan and is where you change it. Only an organization owner sees it.
There are three plans: Free, Pro and the Organization plan. Some features are gated on them, and this documentation says so where it applies. For what each plan costs and includes, see pricing.
If something doesn't work
- You cannot see Billing: only organization owners can.
- You cannot change a published process: only team admins can.
- Adding somebody as an editor is refused: you are out of paid seats. Make them a Viewer, or change your plan.
- Anything else: see Troubleshooting.