License Types, Organization Roles, and Project Roles in Innoslate 4.12.3

Introduction

In Innoslate, access and permissions are managed through a layered system comprising license types, organization roles, and project roles. This structure ensures secure, scalable collaboration across teams and projects. License types determine the overall access model and influence which organization roles can be assigned. Organization roles define a user's high-level privileges across the entire organization, while project roles provide granular control within specific projects. Understanding how these elements correlate is essential for effective user management and workflow optimization.

This article outlines each component and their interrelationships, helping administrators configure access appropriately.

 

License Types

Innoslate offers two primary license types: Named Licenses and Floating Licenses. These licenses are assigned based on user needs and organizational structure, and they directly impact the availability of organization roles. Licenses are managed by organization administrators via the Admin Dashboard.

 

Named Licenses

Description: Named licenses are permanently assigned to specific individual users, providing exclusive and dedicated access that remains available regardless of other users' activity.

Key Features: Ideal for power users, core team members, or stakeholders requiring uninterrupted access. Supports critical or frequent responsibilities without session contention.

Supported Roles: Can be assigned to Users (e.g., Admin Member or Member), Collaborators, Reviewers, or Viewers.

Use Cases: Best suited for dedicated users, such as core engineers or administrators who need consistent, always-on access.

Management: Assigned directly to individuals; no sharing or rotation.

 

Floating Licenses

Description: Floating licenses are shared across the organization on a concurrent basis, allowing a limited number of simultaneous active sessions. When a user logs out, the license becomes available for another user.

Key Features: Cost-efficient for larger teams with occasional or rotating users. Maximizes utilization by managing sessions dynamically.

Supported Roles: Can be assigned to Users (e.g., Admin Member or Member), Collaborators, Reviewers, or Viewers.

Use Cases: Suitable for teams with varying access needs, such as occasional reviewers or part-time collaborators. Encourages users to log out to free up sessions.

Management: Operates on a shared pool; ideal for mixing with Named licenses to balance budget and workflow.

Important Note: The type and number of licenses purchased for your organization dictate which roles can be assigned and how many users can access the system concurrently (for Floating licenses). For example, User Licenses (Named or Floating) are required for higher-privilege roles like Admin Member or Member, while specialized licenses support Collaborator, Reviewer, or Viewer roles. Contact your account representative for pricing and scaling options.

 

Organization Roles

Organization roles establish a user's highest-level privileges across the entire organization. These roles are assigned when adding or managing users via the Admin Dashboard and cannot be customized beyond the defaults. Only users with appropriate licenses can be granted certain roles.

The following table summarizes the available organization roles, their privileges, and license requirements:

Organization Role	Access to Admin Dashboard	Create Projects	Key Privileges	Typical Use Case	License Requirement
Admin	Yes	Yes	Full administrative access, including managing users, teams, roles, schema configurations, licenses, and all projects.	Organization administrators overseeing setup and governance.	Named or Floating User License
Member	No	Yes	Create projects and access shared projects with collaboration capabilities.	Internal team members actively contributing to projects.	Named or Floating User License
Collaborator	No	No	Limited to modifications in assigned projects (write access where permitted).	External or limited contributors needing edit capabilities.	Named or Floating Collaborator License
Reviewer	No	No	View and comment on shared projects; submit change requests.	Stakeholders providing feedback without editing.	Named or Floating Reviewer License
Viewer	No	No	Read-only access to shared projects.	Observers or executives needing visibility without interaction.	Named or Floating Viewer License

 

Management Notes:

• Organization roles are assigned during user addition or via the Users Table in the Admin Dashboard.

• Only the Admin Member role grants access to the Admin Dashboard for comprehensive management.

• Roles are tied to the organization's license configuration—insufficient licenses may prevent assigning higher-privilege roles.

 

Project Roles

Project roles provide fine-grained permissions within individual projects, allowing tailored access for collaboration. These roles are assigned on a per-project basis and are customizable by organization administrators. Project roles apply only to users with the organization role of Member (or lower); Admin Members and SuperAdmins automatically receive Owner privileges in all projects.

Project roles cannot exceed a user's organization role. For instance, a user with a Reviewer organization role cannot be assigned a project role that allows writing.

 

Default Project Roles and Permissions

Innoslate includes the following default project roles, each with a specific set of permissions:

Project Role	Key Permissions	Description
Owner	All permissions: Read, Write, Modify Schema, Create Baseline, Review (Comment), Create Test Cycles, Force Unlock, Share.	Full control over the project, including sharing, deletion, and advanced management. Automatically granted to organization Admins
Collaborator	Read, Write, Review (Comment).	Can view, edit entities, and provide comments. Suitable for active team contributors.
Reviewer	Read, Review (Comment)	Can view content and add comments or change requests. Ideal for feedback-focused users.
Viewer	Read only.	Limited to viewing project content without any modifications or comments.

 

Custom Project Roles

• Organization Admins can create, edit, or delete custom project roles via the Roles Panel or Roles Dashboard in the Admin Dashboard.

• Custom roles are built from any combination of the following permissions: Read, Write, Modify Schema, Create Baseline, Review, Create Test Cycles, Force Unlock, Share.

• New roles default to "Read" permission and can be modified as needed.

• Custom roles are organization-wide but assigned per project.

 

Assignment Process:

1. Open the project and click the "Share" icon.
2. Add users by username/email and select a project role from the dropdown.
3. Users receive an email notification upon assignment.
4. Modify or remove roles via the same dialog.

 

How License Types, Organization Roles, and Project Roles Correlate

The three layers work together to create a flexible yet secure access framework:

• Licenses as the Foundation: License types (Named or Floating) and quantities determine the pool of available roles. For example:

  • User Licenses enable Admin Member or Member organization roles, which support full collaboration.

  • Collaborator, Reviewer, or Viewer Licenses restrict users to lower-privilege organization roles, limiting them to supportive functions.

  • Floating licenses promote efficient resource sharing for variable teams, while Named licenses ensure reliability for key personnel.

  • The organization's license configuration directly limits which organization roles can be assigned, e.g., without Viewer Licenses, Viewer roles cannot be granted.

• Organization Roles Set the Ceiling: These define broad access and act as a cap on project roles. A user's organization role must align with or exceed the intended project role (e.g., a Viewer organization role cannot receive Collaborator project privileges). Admins bypass this with automatic Owner access across projects.

• Project Roles for Granularity: These refine access within projects, allowing admins to assign task-specific permissions without altering organization-wide privileges. Custom roles enhance this flexibility for unique workflows.

• Overall Interdependencies:

  • Scaling and Cost: Mix Named and Floating licenses to optimize for dedicated vs. occasional users, correlating with role assignments (e.g., Named User Licenses for Admin Members).

  • Security and Compliance: Roles ensure users only access what they need, with licenses enforcing capacity limits.

  • Management Flow: Organization Admins (via Admin Dashboard) handle all assignments, ensuring consistency.

  • Example Workflow: An internal engineer (Member organization role with Named User License) might be assigned the Owner project role in their primary project, but Reviewer in others. An external consultant (Collaborator organization role with Floating Collaborator License) is limited to Collaborator project roles.

For advanced configurations or troubleshooting, refer to the Administrator's Guide or contact support. If your organization requires additional licenses or role customizations, reach out to your SPEC Innovations representative.

To continue learning about Licenses and Users, Click Here.

(Next Article: Manage Licenses)