> For the complete documentation index, see [llms.txt](https://docs.bsure.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.bsure.io/v1/user-guides/users/guests.md).
# Guests
Report showing active and inactive guest users. Entra ID guest accounts are external user accounts invited to your tenant/EntraID where they typically have access to Teams or Sharepoint sites.
### Top filter menu
**Users:** \
Showing the total number of guest users according to your filtering selections.
**User Purpose:**\
The user purpose for guest users is set to Guest.
**Created Date & Last Sign-in Date:**\
Set periods for when users where created/invited or their last sign-in date.
**User State:**\
**- Active** - guest users having signed in the last 90 days\
\- **Inactive** - guest users that has not signed in the last 90 days
**Sign-in Status:**\
Filter for guest users that have **Never signed in** and guest users that have **Signed in**.
**Domain Type:**\
Filter for if the guest account is from a **Managed** or **Unmanaged** domain. [Read here](https://learn.microsoft.com/en-us/entra/identity/users/clean-up-unmanaged-accounts) for more information.
**Mail Domain:**\
Filter for guest users from specific mail domains.
**User Principal Name:**\
Free text search for a guests user name. Report will update accordingly.
### Focus and Breakdown section
The **Focus Table** shows the distribution of **active** and **inactive** guests. The **Breakdown Table** shows the distribution of guests from different mail domains.
### User details table with column selector
The **user details table** lists all guest users in scope of your filtering selections. The table has a default set of columns. You can change these to your preferences using the **columns selector**.
---
# 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.bsure.io/v1/user-guides/users/guests.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.
