Skip to main content
Two sidebar pages own workspace-wide state, and both apply across environments (the Staging/Production toggle shows no selection on them): Configuration holds the connections Platinur runs on; Settings holds your profile, preferences, and team.

​
Configuration

Three connection cards, each with its own status pill:

​
Data Warehouse

The analytical database your workspace builds on. Connect workspaces enter and test their customer-owned ClickHouse credentials; Managed workspaces arrive with the selected dedicated service already provisioned and bound. See Connect Your Data Warehouse.

​
GitHub

The governed repository behind staging and production. Connect with one click via Install on GitHub (the Platinur GitHub App); the repository itself is created and initialized automatically at your first apply. Manual repository + access-token setup exists only as a fallback. Under Advanced: write mode (pull request / direct commit), branch prefix, the staging branch (default staging), the production branch (default main), and the dbt/Evidence project paths. See Connecting GitHub.

​
Assistant

Platform-supported AI is included with every workspace — the assistant works out of the box, subject to a monthly fair-use allowance. Optionally add your own OpenAI API key; a customer key takes precedence over the platform-managed project key and is not metered by the fair-use cap. See Data Boundary for exactly what reaches the model provider.

​
Settings

​
Your account

The account strip shows your name and email and provides Sign out. Profile and password changes live in your own row under Team Access. If you forget your password, the login page’s Forgot your password? sends a single-use, one-hour reset link to your email.

​
Preferences

Workspace-wide display preferences: date format, time format, and timezone. The Assistant is always the landing page after sign-in.

​
Team Access

Every signed-in user can see the workspace directory and edit their own name or change their own password. Password changes require the current password and can sign out other sessions. Platinur v1 has three access levels:
  • Owner — the protected primary workspace contact. The Owner has Member capabilities and can invite people, change access, deactivate or remove memberships, send secure password-reset links, and transfer ownership.
  • Member — can use the full product workflow, including creating proposals and Publishing.
  • Viewer — read-only product access. Viewers can ask the Assistant questions, but cannot create proposals, run changes, or Publish.
New people join by email invitation and choose their own password. Owners never create, see, or copy another person’s password. A pending invitation can be updated, resent, or revoked. Removed memberships retain their identity for audit history and can be invited again later. Ownership is transferred from the target Member’s Team Access row. The target must be active and email-verified; both people are signed out after the atomic transfer. If the current Owner is unreachable, contact Platinur support for the private, audited ownership-recovery process.

​
Notification Preference

Where failures and events get delivered — Slack or email — plus a shared What to send list that picks which events fire. Each channel is testable in place. See Notifications.

​
Delete account

Only the Owner sees the danger zone. Delete account permanently removes the Platinur workspace, its models, dashboards, history, routing, stored warehouse credentials, and dedicated AI project. GitHub repositories and customer-owned ClickHouse services and data are not changed. The confirmation names exactly what to type: the current workspace name. Deletion also requires the Owner’s current password and an explicit acknowledgment. It runs asynchronously after acceptance and cannot be undone. V1 does not offer an in-place account reset or warehouse unbind—delete the workspace and create a new paid workspace when you need a completely clean start.

​
Support

Support is a separate sidebar page. Download a redacted diagnostics bundle—status, configuration, recent runs, and schema drift—to attach to a support request. It never contains secrets.