View Seats

Software Factory separates organization capacity into Full seats and View seats. A person’s organization role determines which seat pool they use and which project roles they are eligible to receive.

Full and View capacity are tracked separately. Changing someone between Member or Administrator and View moves them between the two seat pools.

A View member can:

• Belong to the organization and read organization usage
• Access projects explicitly assigned to them
• Use the built-in Viewer project role
• Use a Viewer-compatible custom role
• Perform the Viewer actions available in each assigned module

A View member cannot:

• Create or copy projects
• Receive built-in Editor or Owner
• Receive a custom role containing Editor-level module access
• Manage organization members, role definitions, policies, or billing
• Receive automatic access to every project in the organization

A View seat enforces a Viewer-level ceiling; it does not change the actions included by Viewer.

Viewer-level access currently includes several deliberate exceptions:

• Artifact Viewer can upload and create artifacts.
• Feedback Viewer can submit feedback.
• Automation Viewer can execute an existing automation.
• Project Viewer can list and create project API keys and delete keys they created.

Review Permissions ReferencePermissions Reference before assigning View seats when those actions matter to your access policy.

A custom role is Viewer-compatible when:

• Base Project Access is No Access or Viewer.
• Every module is configured as No Access or Viewer.
• No module includes Editor-level access.

For example, a No Access-based Requirements Reviewer with Requirements Viewer is compatible. A Requirements Editor is not.

Software Factory prevents an assigned Viewer-compatible role from being changed to Editor-level access while it is referenced by a View member or pending View invitation.

Organization Administrators can assign View access when inviting a person or editing their organization role:

1. Open Settings → Organization → Members.
2. Invite a person or edit an existing member.
3. Choose View as the organization role.
4. Assign built-in Viewer or a Viewer-compatible custom role for each project.
5. Save the invitation or membership change.

Editor-level and Owner-level project choices remain visible but disabled. Their tooltip explains that View seats can only receive up to Viewer-level permissions.

Changing an existing Member to View is blocked until every current project assignment is Viewer-compatible.

Active members and outstanding invitations both consume capacity in their selected seat pool:

• Administrator and Member use Full-seat capacity.
• View uses View-seat capacity.
• A pending invitation reserves its selected seat before the invitation is accepted.

If the destination pool is full, an Administrator must add capacity, revoke an unused invitation, remove a member, or choose another eligible organization role before completing the change.

For Team Plan organizations, Full and View quantities are managed separately from Settings → Organization → Details → Manage Seats. View seats are currently configured at $0/month; the price displayed in Manage Seats is authoritative for the subscription.

• Roles and Access ControlRoles and Access Control
• Project RolesProject Roles
• Custom RolesCustom Roles
• Permissions ReferencePermissions Reference