Roles, Permissions, Packages, and Licenses in Newforma Konekt

Every user in Newforma Konekt has two roles: a hub role, which governs hub-level permissions, and a project role, which governs permissions within a specific project.

The package assigned to a hub sets which activity centers are potentially available to that hub’s users. From there, each user’s combination of hub role and project role narrows down what they can actually do within the hub and its projects.

How Packages Work

The package assigned to a hub determines which activity centers are available to users on that hub.

Newforma Konekt currently supports three main packages:

• Info Track: Base package required for every hub.
• BIM Track: Add-on for BIM-related activity centers.
• CA Track: Add-on for contract administration activity centers.

Packages take precedence over project role permissions. For example, a project’s Editor or Admin, who has the permission by default to work in the viewer, cannot do so if the hub doesn’t have the BIM Track add-on.

How Roles Work

Every user holds two roles at all times: one at the hub level and one at the project level.

Hub Roles

A hub role is one of the two roles every user holds (the other being their project role).

A hub role determines whether a user can manage hub-level settings, invite users to the hub, create projects, and access the subscription page, among other

There are three hub roles:

• Hub Owner: Assigned to the creator of the hub. Can perform every hub management function, namely all actions across every page under Hub Menu.
• Hub Admin: Can perform user and project management functions for the hub. Can access every page under Hub Menu, but can’t perform every action in them.
• Guest: Cannot perform any actions at the hub level. Cannot access the pages under Hub Menu.

Each hub can have only one Hub Owner. They’re automatically added to every project in the hub with Admin-level (project role) permissions.

Permissions of Hub Roles

The table below breaks down hub role permissions in more detail.

Permission	Hub Owner	Hub Admin	Guest
Delete hub	✔
Add/remove users	✔	✔
Import users into a project with a CSV file	✔	✔
Create/delete projects	✔	✔
Access the subscription page	✔	✔
Whitelist internal user domains for project access	✔	✔
Enforce Microsoft SSO	✔	✔
Generate API access token	✔

Project Roles

A project role is the other of the two roles every user holds, alongside their hub role.

A project role determines what a user can see and do within a specific project (i.e., whether they can access or work within an activity center). A user can have a different project role for each project in the hub.

There are five project roles:

• Reviewer: Can access shared items and weigh in on project decisions that need their input. Cannot access activity centers outside their workflow.
• Reader: Provides view-only access. Can see and download content from all activity centers but can’t work in them.
• Editor: Provides broad working access for day-to-day project contribution. Can create and manage project content and respond to items that need their input, but can’t perform project administration functions.
• Admin: Can perform all Editor-level actions, plus project administrative functions.
• Creator: Has the same permissions as Admin, and is automatically assigned to the user who creates the project. Can also assign other users within the project as Admins.

Permissions of Project Roles

A user’s project role determines which activity centers they have access to and what they can do within them. See the permission structure of each project role for each activity center:

• Issues
• Change management
• Submittals
• RFIs
• Emails
• Channels
• Files
• Sharing center
• Document control
• Viewer

How Licenses Work

A license is required for any user whose combination of hub role and project role is not Guest (hub role) and Reviewer (project role) across every project they have access to. Users assigned the Guest hub role and the Reviewer project role on all of their projects do not require a license.

Any other combination of roles — including Reader, Editor, or Creator/Admin project roles, or Hub Owner or Hub Admin hub roles — requires a license.

Licenses are purchased with an Info Track subscription, plus any BIM Track or CA Track add-ons you select, in the quantity your organization needs.

Putting It All Together

The following examples show feasible combinations of package, hub role, and project role, and how they combine to determine access and license requirements. These are not fixed pairings, as any package, hub role, or project role can combine with any other.

Scenario	Hub Package	Hub Role	Project Role	License Required	Resulting Access
External consultant reviewing shared items	Any†	Guest	Reviewer on the projects they have access to	No	Can view and respond only to items shared or forwarded to them. Cannot access most activity centers, including the viewer.
BIM modeler	Info Track + BIM Track + CA Track	Guest	Editor on the projects they have access to	Yes	Can log RFIs, submittals, and change management items, and work in the viewer. Cannot manage project settings or archive issues, and cannot access hub settings.
BIM modeler on a hub without BIM Track	Info Track + CA Track	Guest	Editor on the projects they have access to	Yes	Can log RFIs, submittals, and change management items but cannot access the viewer, because the hub’s package doesn’t include BIM Track.
Internal project manager	Info Track + BIM Track + CA Track	Hub Admin	Creator on the projects they have created; Admin on others	Yes	Full project-level access, including managing project settings and archiving issues, plus hub-level access to invite users and create projects. Cannot delete the hub.
Anonymous whitelisted reader	Any†	Guest	Reader on all limited projects in the hub	Yes	Can access and view the activated activity centers of all limited projects. Excluded from all workflows.

†The hub’s package is not relevant to the scenario.

Related Items

• Roles and Permissions Feature Overview
• Create and Manage Custom Project Roles