spec 1 linked patterns checked
Slack Developer Docs: User presence and status
Documents active and away presence values, automatic away detection, manual away behavior, users.setPresence, automatic status reset behavior, and the limit that applications cannot force a user to active.
Read with a purpose
What this source can teach
Use this source to check a technical or accessibility requirement against its exact wording and scope.
- Start with the original. Open the source and find the guidance or example relevant to your task.
- Trace the connection. Use the claim notes below to see how this site applies the source to specific patterns.
- Check the setting. Compare the source's platform, people, and constraints with your own decision.
Pattern Decisions This Source Supports
| Pattern | Supported decision | Required contract | Claim note |
|---|---|---|---|
| Presence | Choose presence when the user needs a transient availability, co-attendance, last-seen, or active-viewer signal attached to a person, group, file, channel, task, or conversation. | Presence badges identify the person or group, status label, recency, and source in text, not color alone. | Slack Developer Docs model user presence as active or away, with automatic and manual away behavior and limits on forcing active presence. |
Comparisons supported by this source
- Presence vs mentions vs notification center vs activity log
Slack Developer Docs model user presence as active or away, with automatic and manual away behavior and limits on forcing active presence.
Evidence Role
This source is treated as spec evidence. Its value comes from the specific claims and setting described above.
Publisher: Slack Developer Docs. Last checked: .