Access Requests

You need to reach a platform resource directly — a Kubernetes namespace or a
database — and you do not have standing access to it. This article covers the
whole path: logging in to SVIEW, raising an access request, getting it
approved, and using the access once it is granted.

Logging in to SVIEW

Your organisation's administrator sets up single sign-on for your team. Once it
is configured, you can log in to SVIEW with one of:

• Google
• GitLab
• Microsoft Entra ID

Log in at your organisation's SVIEW URL. You land on the Environments
dashboard, which shows the health, compliance, and stage of each environment
your team can see.

Why access requests exist

Direct access to production databases and cluster namespaces is not open by
default. Instead, you request it in SVIEW, an approver reviews it, and Teleport
issues short-lived credentials. This gives a full audit trail and keeps
production access intentional and time-bounded.

What does not need an access request

Provisioning a new database, cache, or other Component is self-service. You do
that directly from the Catalog, described in Key Concepts. Only direct
connections — a database session, or kubectl against a namespace — go through
an access request.

Raising a request

1. Go to Access requests in the left-hand menu.
2. Click New request.
3. Select the resource type — Kubernetes namespace, database, or another
   service.
4. Choose the role you need.
5. Add a reason. It is optional, but it appears in the audit log and usually
   speeds up approval.
6. Click Create.

Your request status changes to Pending.

Getting the request approved

A teammate who holds the Approver role in your organisation can approve the
request. If no internal approver is available, CTO2B support can approve it.
Approvals can be made in SVIEW or through the Slack approval flow.

Once approved, the status changes to Approved and Teleport issues temporary
credentials.

Using approved access

• Database access — follow the Connect to a Database guide to connect
  through Teleport.
• Kubernetes namespace access — run tsh kube login <cluster-name> to set
  up your kubeconfig context. See Namespace Access for the
  full sequence.

When access expires

Credentials are valid only for the duration shown on the access request. When
they expire, raise a new request — access is not extended automatically.

Reviewing past requests

The Access requests screen shows the full history of your team's requests:
pending, approved, denied, and expired. The same history is visible in Audit
Logs.

Related articles

• Kubernetes — Namespace Access
• Connect to a Database
• User Profile