Skip to main content
Back to Integrations
monday.com logo

monday.com

Inventory everyone in monday.com - admins, members, viewers, guests from other companies, deactivated and still-pending people - with their last activity, teams and workspace access, the plan and seats the account pays for, and on Enterprise the audit log: sign-ins, data exports, role and security-setting changes and API tokens viewed. Board and item content is never read.

Questions you can answer 17

Each one is a saved query that ships with ConfigView, reading your monday.com data on your own server. Ask it in plain English, SQL, Slack or the API.

  • Who was made a monday.com admin recently?
  • What monday.com security settings changed in the last 30 days?
  • Has anyone regenerated a monday.com API token?
  • Who are the admins in monday.com?
  • Does anyone outside IT have monday.com admin rights?
  • Which monday.com admins have not been active recently?
  • Which AI apps are installed in monday.com?
  • Who installed an AI agent app in monday.com this month?
  • Who exported data from monday.com this month?
  • Has anyone exported a monday.com board to Excel recently?

What ConfigView collects from monday.com 8

  • Account and Plan

    The monday.com account itself: name, URL slug, plan tier and billing period, the seat count it pays for, how many active members it has, whether it is still on a trial, and which monday products (Work Management, CRM, Dev, Service) it runs.

  • Account Roles

    The user roles defined on the monday.com account - the built-in admin, member, viewer and guest roles plus any custom roles (Enterprise) - so each person's role id in Users can be read as a name.

  • Audit Log

    monday.com's account audit log (Enterprise plan, read by an account admin): sign-ins and failed sign-ins, board and account data exports, file downloads, users invited, deactivated or changed role, team and workspace changes, security and AI settings changes, API tokens viewed or regenerated, and AI agent apps installed - who did it, when and from which IP address and device. Board and item names are never stored. Kept as a growing history.

  • Team Members

    Who belongs to each monday.com team and who owns it, with each person's user type and status - so a guest or a deactivated person still sitting in a team that is shared on boards is visible.

  • Teams

    Teams in the monday.com account: name, whether it is a guest team, when it was created, and who owns it. Teams are how boards and workspaces are shared with groups of people.

  • Users

    Everyone in the monday.com account - admins, members, viewers and guests, including deactivated and invited-but-pending people: their user type, status, when they joined, when they were last active, how they were added (invite, SSO, SCIM, domain sign-up) and which teams they are in.

  • Workspace Members

    Who has access to each active monday.com workspace and how: people and teams, each as an owner or a subscriber (member), with the person's user type and status - so guests in a closed workspace and deactivated owners show up.

  • Workspaces

    Every monday.com workspace the admin can see, active, archived or deleted: name, whether it is open to the whole account or closed (members only), which monday product it belongs to, and when it was created. Workspace descriptions and the boards inside are never read.