Organization Management
Manage organization members, invitations, seats, projects, models, and shared skills and templates.
An organization is a private workspace where teams collaborate across one or more 8090 Software Factory projects. Organizations define membership, seats, usage limits, and the skills and templates shared across projects.
Create an organization
When you sign up for 8090 Software Factory, you create an organization or join one through an invitation. The person who creates an organization becomes its Admin.
To create another organization later:
Open the organization switcher
In the project switcher, select Switch Organization, then select Create Organization.
Name the organization
Enter an Organization name and select Create Organization.
Complete billing if asked
You become the new organization's Admin. If the organization needs billing set up, Stripe checkout opens, and you can use the organization once checkout is complete. Otherwise, 8090 Software Factory switches you to the new organization right away.
Organization settings
Open Settings and look under Organization. The pages you see depend on your organization role:
| Page | What it is for | Who sees it |
|---|---|---|
| Details | Rename the organization. On self-serve plans, also open Manage Seats and Manage Subscription. | Admins |
| Members | Members, invitations, and seats. | Everyone. Only Admins can manage. |
| Models | Turn model providers and models on or off. | Admins |
| Manage Roles | Built-in and custom project roles. | Everyone. Only Admins can create, edit, or delete. |
| Projects | Create, rename, archive, and unarchive projects. | Admins |
| Usage | Token usage and cost. See Usage & Billing. | Admins |
| Published Skills | Skills shared with every project in the organization. | Admins |
| Work Order Templates | The preset templates that shape how work orders are written. | Admins |
| Manage Subscription | Opens your subscription in Stripe. | Admins on self-serve plans |
| Enterprise Identity | Directory Sync status and group role mappings. | Admins, once Directory Sync is linked |
Members and roles
Settings → Organization → Members lists every member with their Email, Organization Role, Joined, Updated At, and Last Login. Admins also see each member's Usage and Limit, and a summary of how many Full and View seats are in use.
Each member holds one of three organization roles:
- View uses a View seat. The member reaches the projects they are assigned and any Internal projects, and can only hold the Viewer project role or a Viewer-compatible custom role there.
- Member uses a Full seat. The member reaches the projects they are assigned and any Internal projects, and can create projects, but can't change organization settings.
- Admin uses a Full seat. The member reaches every project, manages organization settings, members, and billing, and can create projects.
The table below lists organization-level abilities only. What someone can do inside a project, with Requirements, Blueprints, Work Orders, and other modules, comes from their project role.
| Capability | View | Member | Admin |
|---|---|---|---|
| See the organization and reach assigned projects | ✓ | ✓ | ✓ |
| See the member list and role definitions | ✓ | ✓ | ✓ |
| Create projects | — | ✓ | ✓ |
| Invite and remove members, and change organization roles | — | — | ✓ |
| Manage seats and the subscription | — | — | ✓ |
| View usage and set usage limits | — | — | ✓ |
| Manage models, projects, published skills, and work order templates | — | — | ✓ |
| Create, edit, and delete custom project roles | — | — | ✓ |
| Act as Owner on every project | — | — | ✓ |
Admins change a member's role in the Organization Role column. Each member's row menu gives Admins Manage Projects, Configure Usage Limit, and Remove from Organization. Any member can select Leave Organization on their own row.
An organization always needs at least one Admin. The last Admin can't leave, be removed, or change roles until someone else is made Admin.
Grant admin access deliberately
Admins can manage membership, organization settings, shared resources, usage, and billing, and they act as Owner on every project. Reserve this role for the people responsible for the organization.
Invite members
Only Admins can invite members.
Open the invite form
On Settings → Organization → Members, select Invite Member.
Add recipients
Enter up to 100 email addresses in one invite.
Choose access
Pick an Organization Role. For View and Member, you can also choose projects and a project role on each. Admins already reach every project, so there is nothing to choose.
Send
Select Send Invite. For a single recipient, Send & Copy Link also copies the join link so you can share it yourself. Invitations expire after 7 days.
To follow up on invitations, open Manage → Manage Invites on the Members page. Switch between Pending, Accepted, Expired, and Revoked, search by email, or filter by project. A pending invitation has these actions:
- Resend sends the email again and restarts the 7-day expiry.
- Edit Invite changes the organization role and project access before the person joins.
- Copy Invite Link copies the join link. It doesn't change the expiry.
- Revoke Invite cancels the invitation and frees its seat. Revoke Selected and Revoke All cancel several at once.
Seats
Full and View seats are separate pools. Member and Admin use Full seats, and View uses View seats, so changing a member's role between View and Member or Admin also moves them to the other pool.
- Change seat counts from Manage → Manage Seats on the Members page. You can't go below the number of seats in use.
- View seats cost $0, but you still add them in Manage Seats before you can invite View members.
- A pending invitation holds a seat. Expired and revoked invitations release it.
- When a pool is full, the invite form shows Full Seat Limit Reached or View Seat Limit Reached with a link to Manage Seats. An invite to several people goes out only if there are seats for all of them.
Enterprise organizations have no seat limit. For prices and included usage, see Usage & Billing.
Models
Settings → Organization → Models controls which models people in the organization can use. Turn off a whole provider, which also turns off any models it adds later, or turn off individual models. Then select Save Changes. At least one model must stay on.
Fable 5 and Fable 5.1 are off until an Admin turns them on. Turning either one on shows Anthropic's data retention notice, which you confirm with Accept and Enable.
Admins choose which models are available, not which model each person uses. Each person picks their own model in the agent chat, and their new chats start with the model they picked last in that organization.
Projects
Settings → Organization → Projects lists every project in the organization. Admins can:
- Create a project with Create New Project.
- Rename a project or change its description with Edit.
- Archive a project, which hides it from the project selector and makes it unavailable to members. Its connected repositories stay attached, which can keep you from connecting them to another project until you unarchive it.
- Unarchive a project to restore access.
- Filter by Project Status to show Active or Archived projects.
Project visibility
Every project is Private or Internal. The Visibility column on the Projects page shows which.
| Visibility | Who can open the project |
|---|---|
| Private | Only people added to the project, plus organization Admins. |
| Internal | Every active member of the organization, with Viewer access. People added to the project keep the role they were given instead. |
New projects are Private unless you pick Internal under Visibility when you create the project. To change it later, a project Owner opens the project's Settings → Project Details, picks the new visibility, selects Save Changes, and confirms with Change Visibility. Admins can also change it with Edit on the Projects page. Making a project Private removes access for organization members who don't have a role on it.
Admins can always choose Internal. The Members can set visibility switch on the Projects page decides whether project creators and project Owners can too. It is on by default. Turning it off doesn't change projects that are already Internal.
Shared skills and templates
Two kinds of shared content apply across projects:
- Published Skills. When someone publishes a skill from a project's Skills module with Publish to Organization, every project in the organization can add it. Admins review and delete published skills on Settings → Organization → Published Skills.
- Work Order Templates. This page lists templates for a work order's Scope, Title, and Description. The Preset templates supply the starting content of each new project's Work Orders Writing Rules skill. After that, a project changes how its work orders are written by editing that skill.
To reuse your own guidance across projects, publish it as a skill. In organizations that still have blueprint templates from earlier versions, Admins also see a read-only Blueprint Templates page.
Manage your subscription
On self-serve plans, Admins open Manage Subscription from Settings → Organization, from the Details page, or from Manage on the Members page. It opens the Stripe billing portal in a new tab. Enterprise organizations are billed under their agreement and don't see these controls.
Enterprise SSO and Directory Sync
Enterprise organizations can sign in through their identity provider and sync members from their directory. 8090 sets this up with you. After Directory Sync is linked, Admins see Settings → Organization → Enterprise Identity, with the sync status, the synced directory groups, and Group Role Mappings that decide which organization role each group grants.
Synced members are managed in your directory. In 8090 Software Factory, you can't change their organization role or remove them, and they can't leave the organization themselves. The Members table marks these members Managed by directory sync.
Next, learn about Usage & Billing.