Integraph

Organisations

Create and manage Integraph organisations, invite team members, assign roles, and control project access.

Overview

An organisation is the billing and access boundary in Integraph. Every user belongs to at least one organisation — a personal organisation created automatically on sign-up. Team organisations let you share projects across multiple engineers and pool subscription access for a team.

Projects, designs, and tool instances belong to an organisation. Members of an organisation can access all projects within it, subject to their role.

Creating an organisation

  1. Open the account menu (top-right of any page) and select Organisations.
  2. Click New organisation.
  3. Enter a name for the organisation (e.g., “Redwood Structural Engineering”).
  4. Click Create.

The organisation is created and you become its Owner.

Member roles

Every member of an organisation has one of four roles. They form a ladder — each role can do everything the one below it can, plus more.

RoleCan doCannot do
OwnerEverything below, plus: transfer ownership, delete the organisation, set the organisation’s MFA policy, change or remove an Admin, and read the API usage report. There is always exactly one Owner.—
AdminInvite, remove and re-invite members; promote a Member or Viewer to Admin; manage billing, subscriptions and payment methods; assign tool access tiers; create, edit and delete projects; read the API usage report.Change or remove another Admin or the Owner. Delete the organisation. Change the MFA policy.
MemberCreate and edit projects and designs.Delete a project. Manage members, billing or organisation settings.
ViewerRead every project and design in the organisation.Create or edit anything.

:::note[Admin reaches billing] An Admin can manage billing — start a subscription, change payment methods, cancel and reactivate. If you want someone who can run projects but not spend money, Member is the role, not Admin. :::

insufficient_role

A project write was refused because your role in the organisation that owns the project is below the minimum for that action. The response is HTTP 403 Forbidden with code: insufficient_role and a requiredRole field naming the minimum; the title reads, for example, “Member role or higher required to update projects”.

ActionMinimum role
Create or update a project, or change its unitsMember
Delete a projectAdmin

Deletion is held to Admin because it cascades through every design, design option, element and analysis output in the project. Viewers are read-only across the platform. Ask an Admin or the Owner to raise your role, or to make the change for you.

The Admin boundary

An Admin can promote a Member or Viewer to Admin, but cannot then change or remove that person — only the Owner can act on someone who already holds Admin. The rule is about the target’s current role, not the new one:

  • Admin changing a Viewer to Member: allowed.
  • Admin changing a Member to Admin: allowed.
  • Admin changing an Admin to anything: refused — Owner only.
  • Anyone changing the Owner: refused.

Owner and Billing Contact are different

Two distinct things that are easy to confuse:

  • The Owner is a member role. Exactly one member holds it, and it carries the organisation-wide powers in the table above.
  • The Billing Contact is who receives invoices and billing notifications. It is a separate setting on the organisation’s General tab and can be any Owner or Admin who has accepted their invite.

They start out as the same person — whoever creates the organisation — but they do not have to stay that way. A practice might keep the Owner with a director while the Billing Contact is the office manager.

The API usage report is readable by the Owner, any Admin, or the Billing Contact. A Member or Viewer who is not the Billing Contact cannot see it, and will not see the tab.

It lists each member’s calls, consumption, refunds, top-ups and net spend over the selected window, and under each member a breakdown of the API key that drove the spend — its name and prefix, never the key itself, which cannot be recovered once created. A revoked key still appears, marked as revoked: revoking a key stops it working, but the spend it already made remains part of the period’s total. Spend recorded before per-key attribution shipped shows as No key, and is never attributed to a key after the fact.

Inviting a member

Owners and Admins can invite new members:

  1. Open the organisation’s Members page.
  2. Click Invite member.
  3. Enter the invitee’s email address.
  4. Select a Role (Admin, Member, or Viewer).
  5. Optionally assign tool-level access tiers if your subscription has per-seat tool licensing.
  6. Click Send invite (or Invite & charge if a billing delta applies).

The invitee receives an email with a join link. If they do not already have an Integraph account, they will be prompted to create one when they follow the link.

If the email address already belongs to an organisation member, the invite is rejected and you will see a “Already a member” error.

Changing a member’s role

  1. Open the organisation’s Members page.
  2. Locate the member whose role you want to change.
  3. Open the actions menu at the end of their row.
  4. Choose Set as Admin, Set as Member or Set as Viewer.

Owners can change any member’s role except their own. Admins can change Members and Viewers, but not other Admins or the Owner — see The Admin boundary above.

Transferring ownership

Because there is exactly one Owner and only the Owner can delete the organisation or manage its Admins, an organisation whose Owner leaves needs the role moved before they go.

Only the Owner can transfer ownership. From the Members page:

  1. Locate the member who will become the new Owner.
  2. Open the actions menu at the end of their row and choose Transfer Ownership.
  3. Confirm.

The nominated member becomes the Owner and you become an Admin, in a single step — the organisation is never left with two Owners or none.

:::important[Transfer before you leave, not after] You cannot reverse this yourself. Once you are an Admin, only the new Owner can transfer ownership back to you.

Ownership also cannot be transferred on behalf of an Owner who has already left. If the outgoing Owner still has access, do this before their account is closed — otherwise recovering the organisation needs Integraph support. :::

The transfer does not move the Billing Contact. If the outgoing Owner also held that, reassign it separately on the General tab — they remain eligible as an Admin, so change it before removing them from the organisation.

Removing a member

To remove a member from the organisation:

  1. Open the organisation’s Members page.
  2. Locate the member.
  3. Click Remove (or the equivalent action) and confirm.

Removing a member revokes their access to all projects in the organisation immediately. Their past contributions (designs, comments) are retained.

Resending an invite

If an invitee has not acted on their invite, Owners and Admins can resend it:

  1. Open the organisation’s Members page.
  2. Locate the pending member (shown with a “Pending” badge).
  3. Click Resend invite.

Deleting an organisation

Only the Owner can delete an organisation.

  1. Open Organisation settings.
  2. Scroll to the Danger zone and click Delete organisation.
  3. Confirm the deletion. Optionally select Also delete all projects to remove every project, design, and associated data in a single step.

:::important Deleting an organisation is permanent and cannot be undone. Ensure all team members have exported or saved any work they need to keep before proceeding. If you choose not to delete projects, the projects become inaccessible to other members immediately but remain accessible to you until you manually delete them. :::