User roles
A Nexus account can be assigned one or more roles. Roles are independent as they do not stack or inherit from each other, so a user only has the capabilities of the roles they have been explicitly assigned. For example, an Expert who also needs Web API access must be assigned both the Expert and Data Consumer roles separately. To request a role assignment or upgrade, contact support@stellaspark.com.
Client¶
A Client can log in to the Nexus web application to view the maps and themes configured for their organization. This role does not grant Web API or Expert API (database) access.
Data Consumer¶
A Data Consumer can request data from the Nexus Web API using a Nexus Web API token to authenticate requests. This role is required for any programmatic access to Nexus data. See the Data Consumer Guide to get started.
Data Supplier¶
A Data Supplier can upload data to Nexus via the Nexus Web API using a Nexus Web API token. To also upload via the web application, the Client role is required in addition. See the Data Supplier Guide to get started.
Expert¶
An Expert has direct access to the Nexus Database (PostgreSQL) and Nexus Datastore, and can deploy calculations to Nexus.
On activation, an Expert receives:
- Database credentials (host, port, database name, username)
- A Nexus Web API token. This is handy for e.g. inspecting data via the Sync tasks API
- A table listing all calculations they are authorised to deploy, including aliases and input/output schemas
Database access is scoped to the user's organization:
- Read access on the world schema(s) associated with their organization's calculations
- Write access to the calculation sandbox schema(s) belonging to their organization See the Expert API Connection Guide to get started.
Scenario Analyst¶
A Scenario Analyst can create, view, edit, and delete scenarios within Nexus. Access to analysis functionality is restricted to users with this role.