> For the complete documentation index, see [llms.txt](https://support.docstudio.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://support.docstudio.com/user/envelope-invitations-and-completion/how-to-accept-and-open-an-envelope-registered-user.md).

# How to Accept and Open an Envelope (Registered User)

This document describes the process for a registered and authenticated user to accept and interact with an envelope, including opening the invitation and completing required actions.

### Accept an envelope as a registered and logged-in user

1. Open the invitation email and follow the link.
2. On the invitation page, choose how to accept the envelope.

You can:

* select an existing mailbox, or
* create a new mailbox

You’ll be taken to that mailbox, and the envelope will open automatically.

### If your email is assigned to multiple roles

If you have more than one role in the same envelope, you’ll see **Apply mailbox to all roles in envelope** (enabled by default).

* Leave it enabled to assign the selected mailbox to all roles.
* Disable it to assign different mailboxes per role.

When disabled, you’ll get a list of roles. For each role, pick a mailbox now or leave it for later.

### Mailbox selection rules

The mailbox list shows only mailboxes you can access and have permission to fill/send envelopes from.

### Creating a new mailbox

When you create a mailbox, the modal asks for:

* **Account**: You’ll see only accounts you can access and manage mailboxes in.
* **Mailbox name**


---

# 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://support.docstudio.com/user/envelope-invitations-and-completion/how-to-accept-and-open-an-envelope-registered-user.md?ask=<question>&goal=<user_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.