> For the complete documentation index, see [llms.txt](https://docs.usepylon.com/pylon-docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.usepylon.com/pylon-docs/support-workflows/assignment-rules/user-status.md).
# User Status
Allow users to set their status to active, away, or out of office
## Statuses
Pylon has three built-in statuses: `Active`, `Away`, and `Out of office`.
### Custom Statuses
Admins can add workspace-specific statuses, such as "In a meeting" or "Lunch". Each custom status inherits the behavior of a built-in status. Assignment settings list each custom status separately (see [Status and assignment](#status-and-assignment)).
1. Go to **Settings > Workspace > Users** and click **Manage User Data**, then open the **Statuses** tab.
2. Click **Add Status** in the **Available** section for statuses that behave like `Active`, or in the **Unavailable** section for statuses that behave like `Away`.
3. Drag statuses to reorder them, then click **Save**.
Archive a custom status to hide it from the status picker. Archived statuses can be restored from **Archived statuses** in their section. Only workspace admins can edit statuses; other users with access to user settings can view them.
## Setting Status
Users can set their status by clicking their profile and then selecting Change status. Depending on the status they select, they will have additional options they can configure, like how long they will be in that status as well as whether to reassign their issues.
Admins can also set status on behalf of users from **Settings > Workspace > Users**. To change several users at once, select them in the table and use the **Status** action in the bar that appears.
An assignee's status can also be used as a filter in triggers, views, etc. This can allow you to control specific behavior for workflows when a user is active, away, or out of office.
## Status and assignment
Two settings control which statuses can receive automatic assignments. Each one opens a list of every status, including custom statuses, and you pick the ones that are allowed.
| Where | Setting | Default for new teams and actions |
| -------------------------------------------------------------------------------------------------------------------------------------------------- | ----------------------------------------------- | ----------------------------------------- |
| **Settings > Workspace > Teams > \[your team] > Assignment** | **Only assign issues to users whose status is** | **Any status** |
| The **Set issue assignee** and **Set task assignee** [trigger actions](/pylon-docs/platform/triggers/conditions.md#assigning-to-unavailable-users) | **Assign only if the user's status is** | Every status in the **Available** section |
With **Any status**, users are eligible whatever their status. Once you pick specific statuses, a user in a custom status is only eligible if that custom status is selected; selecting the built-in status it's based on doesn't include it. If you select exactly the statuses in the **Available** section, available statuses added later are included too.
When the team setting rules out every team member, the team's [assignment rules](/pylon-docs/support-workflows/assignment-rules.md) decide what happens next, for example leaving the issue in the team queue.
## Status Logs
Open a user from **Settings > Workspace > Users** to see their **Status Logs**: each status change, when it happened, and who set it. Changes made automatically by a synced calendar show the calendar as the source.
## Automatic User Status
User status can automatically switch between `Active` and `Away` via [Support Hours](/pylon-docs/support-workflows/support-hours.md). Assign or create a new support hours to individual users via **Settings > Workspace > Users** or via **Settings > Workspace > Teams**.
Once assigned a support hours schedule, users will automatically become `Active` during their enabled support hours, and will become `Away` after hours.
By default all new users will be assigned `All Hours` and will not automatically switch until a support hours has been selected.
Automatic switching between statuses is overridden when a user manually sets their status to `Away` or `Out of office` indefinitely. To clear the manual override they should return to `Active`.
`Out of office` can also be automatically synced via the [Calendar](/pylon-docs/integrations/calendar.md) integration on a per user basis
---
# 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.usepylon.com/pylon-docs/support-workflows/assignment-rules/user-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.
