Getting Access
This guide covers how your team signs in to SVIEW and how to request the extra access needed for databases and Kubernetes namespaces.
Logging in to SVIEW
Your organization's administrator sets up single sign-on for your team. Once configured, you can log in to SVIEW using:
- GitLab
- Microsoft Entra ID
Log in at your organization's SVIEW URL. You'll land on your Environments dashboard, showing the health, compliance, and stage of each Environment your team has access to.
Requesting infrastructure Access
Some actions — like connecting directly to a database, or getting kubectl access to a namespace — require a short-lived access grant through Access Requests, rather than being available by default.
- Go to Access requests in SVIEW.
- Select the role you need (e.g. a specific database role) and submit a request.
- A teammate with approval rights, or CTO2B support, approves the request.
- Once approved, use the Teleport CLI (
tsh) to connect — see the relevant guide for your service (e.g. Connect to a Database) for exact commands.
Access requests are time-limited and expire automatically — you'll need to re-request access after expiry.
What's already available
Provisioning a new database, cache, or other Component doesn't require an access request — that's done directly through the Catalog, described in Key Concepts.
Updated about 5 hours ago