Use inactive_users.html to generate inactive user reports. It uses only Stack Internal API v3. Keep the assets/ folder beside the HTML file, then open the page in a browser and enter your site URL, API v3 bearer token, and inactivity threshold. No Python installation or web server is needed.
The Python scripts remain in this repository for historical reference only. They use the sunset API v2.3 and are not the supported version of this tool.
- A Stack Internal site and an API v3 bearer token that can read user management data. An administrator may need to grant the token the
manage_userspermission. - An up-to-date browser with network access to your Stack Internal API.
For an Enterprise site, enter its URL, such as https://your-site.stackenterprise.co, or its API base URL ending in /api/v3. For Basic or Business, enter the team URL, such as https://stackoverflowteams.com/c/your-team, or the API base URL https://api.stackoverflowteams.com/v3/teams/your-team.
API v3 authentication uses an Authorization: Bearer token. See the Enterprise API v3 guide or the Basic and Business API v3 guide for token setup.
- Download and unpack this repository, keeping
assets/beside inactive_users.html. - Open
inactive_users.htmldirectly in your browser. - Enter the site URL, bearer token, and number of days. The default is 180 days.
- Select Generate reports, then download any of the three CSV files:
all_users_inactive_for_##_days.csvcontributing_users_inactive_for_##_days.csvnoncontributing_users_inactive_for_##_days.csv
The contributing report includes users with at least one question, answer, article, or comment. The noncontributing report includes users with none of those contributions. Each file contains user identifiers, email (when available), last access date, inactivity duration, account status, reputation, and contribution and vote counts.
The page makes read-only API v3 requests directly from your browser. It does not store the token, send it anywhere other than your Stack Internal API, or upload report data. It clears the token field after each run. The reports can include personal information, so handle downloaded CSV files according to your organization's policy.
The API must allow browser requests from the page's origin. If the browser reports a CORS error, ask your Stack Internal administrator to check the site's API CORS settings. The page will not produce partial reports when an API request fails.
For each inactive user, the page requests user details and a comment count. Large reports can use many API calls and may encounter your site's rate limits.
If you run into a problem, open a GitHub issue. This tool is provided as-is, without warranty.