Set Up Your PushOps Access
The one-time setup a new team member needs to sign in to SVIEW and set up Teleport before requesting database or namespace access.
This guide covers the one-time setup a new team member needs: signing in to SVIEW, and setting up Teleport, before requesting access to databases or Kubernetes namespaces.
Sign in to SVIEW
Your organisation's administrator sets up single sign-on for your team. Once it is configured, you can sign in to SVIEW with:
- GitLab
- Microsoft Entra ID
Sign in at your organisation's SVIEW URL. You land on the Dashboard, which shows the health, compliance, and stage of each Environment your team has access to.
If your identity provider's client secret for SVIEW is about to expire, see Renew an Expiring SSO Client Secret. If you cannot sign in at all, see Cannot Sign In to SVIEW or Teleport.
Set up Teleport
Direct connections to databases and Kubernetes namespaces go through Teleport, which has its own sign-in: your email address, a Teleport password and a second factor. Teleport does not use the single sign-on button you use for SVIEW. Set it up once with Set Up Teleport Sign-In With an Authenticator App or Security Key.
Next steps
- Access to a database or namespace — once you can sign in, request it in SVIEW. See Access Requests.
- Adding or removing people — see Add or Remove a Team Member.
Updated about 1 month ago