Access Controls
Teleport's role-based access control (RBAC) enables you to set fine-grained policies for who can perform certain actions against specific resources. For example, you can allow analytics team members to SSH into a MongoDB read replica, but not the main database. You can also allow SREs to access a production server only when using a trusted hardware device, or if approved by someone else from the same team.
- Getting Started With Access Controls: Get started using Access Controls.
- Getting Started with Access Monitoring: Learn how to use Access Monitoring.
- Access Lists (section): Use Access Lists in Teleport
- Cluster Access and RBAC (section): How to configure access to specific resources in your infrastructure or your Teleport cluster as a whole.
- Compliance Frameworks (section): How to use Teleport's access controls to streamline compliance without sacrificing productivity.
- Configure Single Sign-On (section): How to set up single sign-on (SSO) for SSH using Teleport
- Configure Teleport as an identity provider (section): How to set up Teleport's identity provider functionality
- Device Trust (section): Teleport Device Trust Concepts
- Enroll the Teleport Okta Integration (section): Describes how to set up the Teleport Okta integration in order to grant Teleport users access to resources managed in Okta.
- Just-in-Time Access Request Plugins (section): Use Teleport's Access Request plugins to least-privilege access without sacrificing productivity.
- Just-in-Time Access Requests (section): Use just-in-time Access Requests to request elevated privileges.
- Login Rules (section): Transform User Traits with Login Rules