Product
Product overviewHow it worksFormsFormis AITransmittalsFree templates
Who it's for
Project ManagersProject Engineers & Doc ControlDirectors of Projects
Compare
vs Fieldwirevs Procorevs Unifiervs AutodeskBest RFI software (2026)
More
PricingHelpRework calculatorAboutSecurityContact
Sign inStart free trial

Understand seats and project roles

UPDATED AUGUST 25, 2026 / GETTING STARTED

A seat in Formis is the license type for your Formis tenant assigned to each person (Tenant Admin, Manager, or Contributor). A project role is the job someone holds on one project, such as Project Manager. Assign seats on Team; assign project roles on the project after invite or during setup.

Example

In our sample project, Maple Commerce Center, we give Jordan a Manager seat and the Project Manager project role so they can run RFIs, while keeping Document Controller (the document-register manager role) on someone on the host company.

Before you start

This article is written for Tenant Admins and Managers on the host company, the people who can change these settings.

The three seats

Every person in your Formis tenant has one seat. The invite dialog labels them:

Seat What it covers
Tenant Admin Billing, all users, tenant settings, and full visibility across your tenant.
Manager Build forms and workflows, manage contributors, and (on the host company) see all forms on projects they are assigned to.
Contributor Day-to-day submit and act work, scoped by Access Groups (which form definitions they may open) on each project.

Seats are the license layer. They are separate from the project role someone holds on a given project (for example, Maple Commerce Center).

Screenshot: How permissions work page summarizing Tenant Admin, Manager, and Contributor seats.
See how Tenant Admin, Manager, and Contributor seats differ.
How Formis decides what one person can open on a project. Left: person card for John (Contributor seat, True Line Concrete outside company, Subcontractor project role, Field Forms Access Group) above four levers: seat (license and tenant-wide power; Managers on the host company bypass Access Groups), project role (who workflow steps route to), company (the host company or outside; same-company work is mutually visible), and Access Group (whitelist of form definitions; filters forms only, never documents). Right: Forms outcome shows John can open Request for Information and Daily Field Report, including Greg's RFIs and Dailies because Greg is also on True Line Concrete; a Manager on the host company would see every form on the project instead. Documents outcome lists four doors: own uploads, True Line Concrete (same company), Project-wide access, and transmittal. Never-visible block: pending (needs review) documents and other companies' private project files. Caption: FIG 01, four levers, two outcomes; forms and documents are decided separately.
Four independent levers control each person's visibility on a Formis project: seat, project role, company, and Access Group. Forms and documents are decided separately, so a subcontractor's crew sees their own work without opening the host company's files.

For the Standing and Delivery full picture, see How Formis decides what you can see.

Project roles Formis ships

Built-in project roles (exact display names):

  • Project Member
  • Project Manager
  • Assistant Project Manager
  • Backup Project Manager
  • Document Controller
  • Project Engineer
  • Engineer of Record
  • Architect
  • Owner's Rep
  • Subcontractor
  • Inspector

Shipped roles such as Project Manager and Document Controller carry built-in authorities on the project. You assign them from the project team tools (and Standard project roles in settings when you manage the registry).

How seat and role compose

Some project roles require a Manager or Tenant Admin seat before you can assign them:

  • Document Controller
  • Project Manager
  • Assistant Project Manager
  • Backup Project Manager

If you try to assign one of those roles to a Contributor, Formis shows: "{Role} requires a Manager seat. Assign a Manager seat before giving this project role."

Other built-in roles (for example Owner's Rep, Subcontractor, Inspector) do not require a Manager seat by themselves. Pair them with the seat that matches how much product access the person needs.

Screenshot: Project team assignment with Project Manager selected for a Manager-seat user.
Assign a project role such as Project Manager on the project team.

Why would someone at an outside company have a Manager seat?

An outside Manager seat lets a partner lead their firm's people and act on workflow steps assigned to their project role, without making them part of the host company.

Example

In our sample project, Maple Commerce Center, Dana works for North Arrow Management (the owner's-rep CM firm). We give Dana a Manager seat on that outside company and the Assistant Project Manager project role.

Workflow steps assigned to Assistant Project Manager route to Dana, and she can approve or complete them. She can invite her firm's Managers and Contributors and manage project team assignments when she holds Assistant Project Manager (or Project Manager / Backup Project Manager). Access Groups still scope which forms her firm opens. Pending document review stays with the host company; Dana does not run the pending register queue. For how a routed step can still hand Dana a specific submission (Delivery), see How Formis decides what you can see.

Document Controller and outside companies

Document Controller is available for members of the host company. If someone belongs to an outside company, Formis blocks that role with: "Document Controller is only available for members of the host company. Assign that role to someone on the host company, or mark this company as the host company."

Owner's Rep, Subcontractor, and similar outside-facing roles remain available for partner companies. See Control who sees what on a project and Work with outside partners on a project.

Add a custom project role

Tenant Admins can add custom project roles from Settings → Project Roles (/settings/project-roles).

  1. Open Project Roles.
  2. Click Create Role.
  3. Enter **Key ***, **Display Name ***, optional Description, and **Color ***.
  4. Under Record permissions, set the record flags that apply.
  5. Save.

Custom roles appear in the project team assignment picker and can be used as workflow step assignees. They do not receive built-in Project Manager, Assistant Project Manager, Backup Project Manager, or Document Controller authorities (for example Project-wide detail toggle and document-register manager powers stay on those fixed role keys).

Tip

Open How permissions work (/help/permissions) in the product for the same seat, role, company, and Access Group model in a short in-app explainer.

Related