> For the complete documentation index, see [llms.txt](https://glyue.docs.sandboxbanking.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://glyue.docs.sandboxbanking.com/~/changes/sRNNcOmmdTZIw2Ha7IFP/reference/permissions.md). # Permissions A Glyue user's permissions a governed by three concepts: * [User Type (Standard, Staff, Service Account)](#user-type) * [User Permissions](#user-permissions) * [Group Permissions](#group-permissions) ### User Type | Page | Standard User | Staff User | | ---------------- | -------------------- | -------------------- | | Dashboard | :white\_check\_mark: | :white\_check\_mark: | | Bookmarks | :white\_check\_mark: | :white\_check\_mark: | | Run History | :white\_check\_mark: | :white\_check\_mark: | | Build | :white\_check\_mark: | :white\_check\_mark: | | Swagger API | :white\_check\_mark: | :white\_check\_mark: | | Schedule | :white\_check\_mark: | :white\_check\_mark: | | Vault | -- | :white\_check\_mark: | | Migrate | -- | :white\_check\_mark: | | View Changes | -- | :white\_check\_mark: | | Invite | -- | :white\_check\_mark: | | Admin (settings) | -- | :white\_check\_mark: | A **Standard Glyue** user account is appropriate for everyday users who are involved in the building, maintenance, or monitoring of integrations. A **Staff Glyue** user is equivalent to a system administrator. These users have access to additional pages, notably the *Invite* page, which allows them to invite additional Standard and Staff users into Glyue, and the *Admin* page, which controls settings for the Glyue environment. A **Service Account** is an account created to manage third-party system access to integrations on Glyue. A Service Account is only meant to execute integrations, and cannot log into the Glyue UI, view or edit integrations, or invite other users. Learn more about service accounts here. ### User Permissions Both Standard and Staff users can have their abilities augmented by being granted permissions specific to a particular action. These permissions must be granted by a member of Sandbox staff — reach out to for help. #### Integration Permissions Each user — both Standard and Staff — must be explicitly granted permission to access integrations. This must be done for each integration. Typically this is handled by your Sandbox Solution Engineer — reach out to for help. Integrations come with four separate permission types: Read, Write, Execute, and Debug. Details on these can be [found here](/~/changes/sRNNcOmmdTZIw2Ha7IFP/reference/integration_configuration.md#integration-permissions). ### Group Permissions Groups may have additional permissions granted to them. Any member of the group automatically receives these permissions when they become a member of a group, and the permissions are revoked if the user is removed from the group. Permissions granted through a group are only additive to any existing permissions a user has. Groups and Group Permissions are typically managed by Sandbox — reach out to for help. --- # 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 dynamically by asking a question. Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter: ``` GET https://glyue.docs.sandboxbanking.com/~/changes/sRNNcOmmdTZIw2Ha7IFP/reference/permissions.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal. 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.