> 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/how-to-guides/how-to-invite-new-users.md).
# How to Invite New Users
1. Navigate to the *Invite* page. This page is only visible for Staff users.
The Invite page icon in the navigation menu
2. Enter the new user's email and give them a username. The invitation will be sent to this email.\
\
Selecting "Staff" in the *Additional Permissions* dropdown will give the user [Staff permissions](/integration-gateway-platform-reference/permissions.md#user-type).
{% hint style="info" %}
If you're unsure what username to give, we recommend reusing the portion of their email before the @ sign.
{% endhint %}
3. Select the integrations that the user should have access to. You will need to grant each [type of permission](/integration-gateway-platform-reference/integration_configuration.md#integration-permissions) separately.
The Integration Permissions page of the User Invitation wizard.
4. Click *Save* to send the invitation.
***
Invitations are valid for 14 days from when they are created. If an invitation expires, the recipient can still follow the link to request a new invitation, which will be sent to the original email.
---
# 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://glyue.docs.sandboxbanking.com/how-to-guides/how-to-invite-new-users.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.
