> For the complete documentation index, see [llms.txt](https://help.meltingspot.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://help.meltingspot.io/english/manage-spot/audience/members/members-status.md). # Member's status Declined, Rejected, Deactivated... What is the difference? On your Spot, members can have different statuses. Each status has a different meaning. There are 7 in total:

Status	Conditions	Access
Accepted	A member has an `Accepted` status if he/she registers on a public Spot, accepts an invitation to join the Spot or if an admin validates his/her registration request on a private Spot.	The member has access to all the content of the Spot except for private content to which he/she is not invited (certain live, channels, collections, etc.).
Invited	A member has an `Invited` status if they have been invited by an admin to join the Spot. 👉 Invite members	The member only has access to the home page and to the list of lives whose privacy are public.
Pending	A member has a `Pending` status if they have requested to join a private Spot.	The member only has access to the home page and to the list of lives whose privacy are public.
Declined	A member has a `Declined` status if they have declined an admin's invitation to join the Spot.	The member only has access to the home page and to the list of lives whose privacy are public.
Rejected	A member has a `Rejected` status if an admin has refused their request to register on a private Spot.	The member only has access to the home page and to the list of lives whose privacy are public.
Deactivated	A member has a `Deactivated` status if an admin has deactivated their profile.	The member only has access to the homepage and to the list of lives whose privacy are public.
Left	A member has a `Left` status if he/she decides to leave the Spot.	The member only has access to the homepage and to the list of lives whose privacy is Public.

### Member status update rules on registration or connection When a member registers or connects to a Spot, his status might be updated. Here are how it works, with slight differences depending on the authentication method used: * [Registration with a password](#inscription-via-mot-de-passe) * [Registration via SSO](#inscription-via-sso) * [Connection with a password](#reconnection-via-mot-de-passe) * [Connection via SSO](#reconnection-via-sso) {% tabs %} {% tab title="Registration with a password" %}

{% endtab %} {% tab title="Registration via SSO" %}

{% endtab %} {% tab title="Connection with a password " %}

{% endtab %} {% tab title="Connection via SSO" %}

{% endtab %} {% endtabs %} ### Member status updated by the admin Admins can update the member's status in the following cases:

--- # 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://help.meltingspot.io/english/manage-spot/audience/members/members-status.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.