> For the complete documentation index, see [llms.txt](https://docs.groundcover.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.groundcover.com/administer.md). # Administer - [Role-Based Access Control (RBAC)](https://docs.groundcover.com/administer/role-based-access-control-rbac.md) - [Billing](https://docs.groundcover.com/administer/billing.md): The Billing page helps you manage your groundcover subscription, view current pricing plans, and monitor node usage across your infrastructure. You can access it from Settings > Billing. - [Okta SSO](https://docs.groundcover.com/administer/okta-sso-onboarding.md): To connect your Okta tenant as an identity Provider in groundcover, you must create an OIDC application - [Okta Roles Integration](https://docs.groundcover.com/administer/okta-sso-onboarding/okta-roles-integration.md) - [API Keys](https://docs.groundcover.com/administer/api-keys.md): An API key in groundcover provides secure, programmatic access to the API on behalf of a service account. It inherits that account’s permissions and should be stored safely. - [Service Accounts](https://docs.groundcover.com/administer/service-accounts.md): A service account is a non-human identity for API access, governed by RBAC and supporting multiple API keys. --- # Agent Instructions This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com. ## Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation by asking a question. Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters: ``` GET https://docs.groundcover.com/administer.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.