The Roles tool defines the functional position a user holds within a project. It allows firms to design and structure their internal operational roles in a fully customizable way inside Neostella.
Roles serve as a structured directory of responsibilities within the firm. Once created, roles become available within the Cases workspace when assigning users to projects.
This tool is designed for administrators and serves as a foundational configuration component within Access.
Roles do not control system permissions or security access. They define how users participate in projects, not what actions they can perform within the platform.
purpose of roles
Roles exist to help firms model their internal structure inside Neostella. Instead of relying on rigid system-defined roles, the Roles tool allows firms to:
- Design roles that reflect their real-world operational structure.
- Assign roles based on user type.
- Align roles with specific project types.
- Maintain consistency when assigning users to projects in Cases.
Roles function as a structured reference system for how people participate in projects.
In addition, roles can be used to determine which subobjects within a project are visible to specific users. This configuration is not managed through Permission Sets. Instead, it is defined at the object level within the Display tab, where role-based visibility rules are configured.
how roles work in neostella
Roles are independent configuration records within Access. They are:
- Not connected to Permission Sets.
- Not dependent on Users.
- Not tied to Groups.
Instead, Roles serve as a structural classification layer that:
- Defines a role name.
- Associates that role with a specific User Type.
- Associates that role with a specific Project Type.
Once configured, roles become available for assignment within project-related workflows.
role classification by user type
Roles classify users into four primary categories. Each role must be associated with one of these user types to ensure alignment with system-wide user classification.
| User Type | Description |
| Full | Internal users with complete participation within projects and firm operations. |
| Collaborator | Internal or external users with limited, task-based participation. |
| Guest | Users with restricted visibility or temporary access within projects. |
| Partner | External firm collaborators or partner-level participants associated with projects. |
roles within project structure
Roles serve as a structural bridge between users and projects. When working inside the Cases workspace:
- Users can be assigned to projects using predefined roles.
- The role defines the user’s functional position within that project.
- The configuration ensures consistency across projects of the same type.
This allows firms to standardize project participation while maintaining flexibility in internal role design.