Permissions and limits
What Seatwise can't see or change
Jira doesn't let apps see or change everything. Seatwise says plainly where its view ends, so you know what to check yourself.
- Seatwise never deletes or deactivates accounts. It changes Jira group membership only.
- It doesn't manage Confluence seats.
- Jira doesn't give apps a last-login date. Seatwise shows last Jira work, or the last-seen date from Atlassian's user export.
- Work that Seatwise can't read doesn't count as Jira work, for example work items hidden by issue security.
- Apps can't change filter subscriptions. The subscriber can, or you can in the filter's settings.
- Apps can't see other people's private dashboards. Ask the person, or check by hand.
- Apps can't change groups that your identity provider manages, such as Okta or Microsoft Entra ID.
- Seatwise learns this when Jira refuses a change. It then marks the group and tells you to change it in your identity provider.
- Seatwise doesn't check Automation rules, approvals in Jira Service Management, Assets or global permissions for group use.
- Seatwise doesn't remove people on a schedule. A site admin always chooses to remove.
- Atlassian doesn't tell apps your plan or price, so you enter them in Settings.
What you should see
You know which checks Seatwise does for you and which ones stay with you.
If something is not right
Someone still has Jira after a cleanup. Someone may have added them back, or another group gives them Jira. Open the cleanup from History and choose “Recheck now”.
Still stuck? Write to [email protected].