> For the complete documentation index, see [llms.txt](https://docs.appmysite.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.appmysite.com/app/team/accept-team-invite.md).

# Accept team invite

Collaborating with your team on AppMySite begins with a simple invitation process. If someone has invited you to join an app project, follow the steps below to accept the invitation and get started.

#### Step 1: Open your email invitation

* Check your inbox for an email from AppMySite.
* The email will include a button labeled **Accept invite**.

{% hint style="warning" %}
If you don't see the email, check your spam or junk folder.
{% endhint %}

#### Step 2: Accept the invitation

* Click on the Accept invite button in the email.
* You will be redirected to app.appmysite.com.

{% hint style="warning" %}
Make sure to sign in or sign up using the **same email address** the invitation was sent to.
{% endhint %}

#### Step 3: Sign up or log in

* New to AppMySite? Complete the sign-up process with your credentials.
* Already have an account? Simply sign in using your existing details.

Once logged in, your access to the app will be activated automatically.

#### What happens next?

After accepting the invite and signing in:

* You’ll be added as a team member on the app.
* Your access and permissions will depend on the role assigned by the inviter.
* You can view the app on your dashboard and begin contributing immediately if your status is set to Active.


---

# 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.appmysite.com/app/team/accept-team-invite.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.