Getting Started
From first sign-in to your first approved golden record in about fifteen minutes. This guide walks the complete cycle once, so every other page in the documentation has context.
Before you start
Rapida MDM 2.0 runs as a Streamlit-in-Snowflake application, so there is nothing to install on your machine. You need three things:
- An active Snowflake account where the application has been deployed.
- A Snowflake user with permission to query the
MDM_ONE.COREschema. - A modern web browser: Chrome, Edge, Firefox, or Safari.
Your administrator will share the application URL. Open it and sign in with your Snowflake credentials, the same ones you use for Snowsight.
Understanding first-time access
The very first time the application runs in a Snowflake account, it starts in bootstrap mode: every authenticated user is temporarily treated as a SuperAdmin with full access. This exists so the first person in can set things up without a chicken-and-egg permissions problem. Bootstrap mode ends the moment the first user assignment is created in Settings → Users. From then on, everyone is governed by the role they have been granted.
The fifteen-minute tour
The fastest way to understand the platform is to run one full governance cycle yourself: define a domain, create a record, and approve it. Here is the end-to-end path.
-
Create an enterprise
Open Enterprises in the sidebar and click + Create Enterprise. Give it a name, say Acme Australia, and an optional description. The enterprise is the tenant that scopes everything you create from here on.
-
Define a data model
Open Data Models and click + Create Data Model. Pick your new enterprise and name the model, for example Customers. A data model is simply a logical grouping for one or more related tables.
-
Add a table
Inside the data model, click + Add Table and name it, for example Customer Master. The table is the concrete entity that will hold your records.
-
Define the attributes
Open the table's Attributes screen and create at least one attribute marked as a Business Key: the field that uniquely identifies each record, such as Customer ID. Then add whatever other fields you need, each with an appropriate data type.
-
Create your first record
Go to Records, select your enterprise, data model, and table, then click + Add Record. Fill in the form and save. Notice the record arrives in Pending state: nothing becomes trusted data without review.
-
Approve it
Still on the Records screen, tick the new record's checkbox and click Approve. The status flips to Golden. You have just promoted your first master record. From now on, every change to it will create a new pending version for review, while the golden version stays protected.
Where to go from here
Assign data stewards
Use the Responsibilities matrix to make explicit who enters and who approves data on each table.
Import existing data
Load your current records in bulk from CSV or Excel with Import & Export, including column mapping and validation.
Connect Snowflake sources
Schedule automatic pulls from other Snowflake tables with Integrations.
Make it yours
Set your logo, application name, and color theme in Settings.
Common questions
I signed in and I can see everything. Is that right?
If no user assignments exist yet, the application is in bootstrap mode and every authenticated user has full access. That is expected on a fresh installation, but it should be closed off promptly by creating the first SuperAdmin assignment in Settings → Users.
Why did my new record not appear as Golden immediately?
By design, no record enters the system as Golden. New records, whether typed in or imported, always start as Pending and must be approved. This guarantees every golden record has passed through review.
Do I have to follow the exact order in the tour?
The hierarchy makes the order natural: a data model needs an enterprise, a table needs a data model, and attributes need a table. You can always come back and add more of any of them later: nothing about the initial setup is locked in.
Which credentials do I use to sign in?
Your normal Snowflake credentials: the same username and password (or SSO) you use for Snowsight. Rapida MDM 2.0 does not maintain a separate user directory.