About Spatial Studio User Roles

Learn about the different user roles supported in Spatial Studio.

The following application roles are supported in Spatial Studio:

• SPATIAL_ADMIN

• SPATIAL_AUTHOR

• SPATIAL_CONSUMER

It is important to note that all the role names are case sensitive. When granted to a user, these roles allow the user to access the various features and services of Spatial Studio, governed by the rules described in the following sections.

Administrator: SPATIAL_ADMIN

A user with the SPATIAL_ADMIN role is considered the system-level administrator of the accessed Spatial Studio instance, irrespective of all other roles they may hold.

A user with a system-level administrator role is not recommended for performing regular development or analysis work while inside Spatial Studio. An admin user’s responsibilities are the following:

• Change global or instance-wide settings such as banner customization, custom base maps or safe domains.

• Monitor and view system logs if your Spatial Studio instance is connected to a compute environment.

Regular User: SPATIAL_AUTHOR

A user with role SPATIAL_AUTHOR (but not SPATIAL_ADMIN) is considered a regular user.

A regular user role allows the user to:

• Create various Spatial Studio objects such as connections, datasets, and projects.

• Create spatial analyses.

• Publish projects and add custom map icons.

Read-Only User: SPATIAL_CONSUMER

A user with the SPATIAL_CONSUMER role is considered a read-only user and is prohibited from creating, modifying or removing any permanent objects (such as datasets, connections, spatial analyses, write-access tokens, and so on) within Spatial Studio.

A user with the SPATIAL_CONSUMER role is allowed to:

• Create a new project from existing datasets.

  However, the new project cannot be saved or published.

• Perform data visualization activities within the currently logged in session.

Note: A user is a read-only user if SPATIAL_CONSUMER is the only role granted to them. If a user has both SPATIAL_CONSUMER and any other role (such as SPATIAL_AUTHOR), then those other roles with greater privileges will take precedence.

The following describes a few use cases that apply for the SPATIAL_CONSUMER role:

• As seen in Regular User: SPATIAL_AUTHOR, a user with SPATIAL_AUTHOR role can create projects and datasets within Spatial Studio. Once the project(s) are finalized, the Spatial Studio administrator may change the user’s role to contain only SPATIAL_CONSUMER, effectively freezing the projects from being modified (accidentally).

• Another use case of such a role is for read-only users to be able to visualize publicly available datasets for information purposes without creating permanent projects that can potentially consume a lot of resources in Spatial Studio.