Settings

The administrative home of Rapida MDM 2.0: brand the application, configure the email integration behind alerts, and, most importantly, control who has access to which enterprises.

Settings is organized into three tabs:

General — application name, logo, and email integration.
Appearance — sidebar theme presets.
Users — user-to-enterprise role assignments.

General

Application name

The text entered here appears in the sidebar header, useful for branding the application with your company's name, such as Acme MDM 2.0. Click Save Changes to apply.

Snowflake email integration

Email alerts sent from the Responsibilities page travel through a Snowflake notification integration. Enter that integration's name here (the default is EMAIL_INT). Your Snowflake administrator can create one with a few lines of SQL:

CREATE NOTIFICATION INTEGRATION EMAIL_INT
  TYPE = EMAIL
  ENABLED = TRUE
  ALLOWED_RECIPIENTS = ('your.team@example.com');

Application logo

Upload a PNG, JPG, JPEG, or SVG image to replace the default "R" badge in the sidebar. A square image around 128 × 128 pixels works best. Use Save Logo to apply or Clear Logo to revert.

Appearance

The Appearance tab shows a grid of theme cards with live previews. Available presets include Midnight Blue (the default), Crimson Dark, Classic Red, Ruby Red, Forest Green, Violet Night, Ocean Teal, Amber Dusk, Slate Gray, and Rose Gold.

The active theme is marked with a check; click Apply on any other card to switch. The theme controls the sidebar palette and the accent color for the active navigation item.

Users

The Users tab is where access is actually granted, and where the platform's most important security transition happens.

Bootstrap mode and the first assignment

Before the first assignment exists, every authenticated user has full SuperAdmin access: bootstrap mode. The moment you add the first explicit assignment, the application switches to strict role-based access control for everyone.

Avoid locking yourself out Make your first assignment a SuperAdmin (ideally yourself) before creating any other assignment. Otherwise you may switch on strict access control with no administrator inside it.

Adding a user assignment

The Add User Assignment card (visible to Admins and SuperAdmins) takes three fields: the user's Snowflake Username, the Enterprise the assignment applies to (Admins see only their own enterprises; SuperAdmins see all), and the Role. Click + Add to save. If an inactive assignment already exists for the same user, it is reactivated rather than duplicated.

What each global role can do

Role	Capabilities
SuperAdmin	Full access across every enterprise: all users, all data, all integrations.
Admin	Full access within their assigned enterprises. Can manage users (limited to Editor and Viewer), data, and integrations.
Editor	Can create, edit, and approve records inside their enterprises. Cannot manage users or integrations.
Viewer	Read-only across their enterprises, unless granted table-level stewardship via the Responsibilities matrix.

Who can assign what

Your role	Roles you can assign
SuperAdmin	SuperAdmin, Admin, Editor, Viewer
Admin	Editor, Viewer
Editor / Viewer	No assignment privileges

Looking for Steward or Approver? Those are not assigned here. They are table-level responsibilities managed on the Responsibilities page, and they override a user's global role for the specific tables involved.

Viewing and removing assignments

Below the Add card sits a table of all current assignments (username, enterprise, role, and assignment date), each with a trash-can icon. SuperAdmins can remove any assignment; Admins can remove only Editor, Viewer, Steward, or Approver assignments within their own enterprises.

Common questions

I don't see the Add User Assignment card. Why?

The card is visible only to Admins and SuperAdmins. If you cannot see it, you do not have privileges to grant access: ask one of your existing administrators.

We created assignments and someone got locked out. What now?

An existing SuperAdmin (or an Admin of the relevant enterprise) simply adds an assignment for the affected user. If no SuperAdmin was ever created, your Snowflake administrator can correct the assignments directly in the MDM_ONE.CORE schema, another reason to create that first SuperAdmin before anything else.

Does changing the theme or logo affect other users?

Yes: application name, logo, and theme are platform-wide settings. Everyone sees the same branding, which is the point: one consistent, recognizable governance home for the whole organization.

Can one user hold different roles in different enterprises?

Yes. Assignments are per enterprise, so a user can be Admin of one enterprise and Viewer of another. Their effective rights in any context come from the assignment for that specific enterprise, plus any table-level responsibilities.