Automated Grammarly Seat Audit
Every Monday, WebRun opens the Grammarly admin area, lists who holds a seat and who has never activated one, compares that against the active members of your Slack workspace, posts the gap to Telegram, and leaves an invite list in Slack for an admin to approve.
How do I check who on my team is missing a Grammarly seat?
WebRun audits your Grammarly seats every Monday. It lists who holds a seat, who has an invite still pending, and whose seat has gone idle, matches that against the active members of your Slack workspace, then posts the gap to Telegram and leaves a proposed invite list in Slack for an admin to approve.
- New joiners are spotted without a seat within a week
- Idle seats are surfaced for reclaim instead of renewing quietly
- No invite is sent and no member removed without an admin
Built for IT administrators · operations managers · finance teams · people operations
What does WebRun do on every run?
The exact actions WebRun takes, in order - in plain language, so you can adjust anything.
-
WebRun signs in and gets to work
Opens
app.grammarly.comin a real browser with your saved login - no setup, no API keys. -
1
Grammarly - list seats and pending invites
WebRun opens Grammarly to list seats and pending invites. - Sign into your Grammarly account and open the admin members view
- List every member with their seat status, their group, and whether the invite is still pending
- Note anyone whose seat has shown no activity inside your idle window
- Record the total seats bought against the seats currently assigned
Done when Every seat is listed as assigned, pending, or idle, and the bought against assigned count is known.
-
2
Slack - match against active people
WebRun opens Slack to match against active people. - Open your Slack workspace member directory
- List the active people in the teams that are entitled to a Grammarly seat
- Match them against the Grammarly member list by email address
- Build two lists: people with no seat, and Grammarly seats held by someone no longer active in Slack
- Post the proposed invite list to the admin channel and leave it for a person to approve. WebRun never sends an invite itself
Done when The missing-seat list and the idle-seat list are built, and the invite list is posted for approval.
-
3
Telegram - post the seat gap
WebRun opens Telegram to post the seat gap. - Post the weekly seat gap to your operations channel
- Give the headline first: seats bought, seats assigned, and seats sitting idle
- List the people entitled to a seat who do not have one, and the seats that could be reclaimed
- Note that the invite list is waiting for an admin in Slack
Done when The channel has the seat counts, the missing list, and the reclaim list.
How is each run configured?
Secure by default
Connect once, stays signed in
WebRun signs in once and keeps each session in a persistent environment, so every run picks up right where it left off.
Every action is checked against this policy before it runs.
Questions, answered
Will it invite people or remove seats on its own?
No. WebRun prepares the invite list and the reclaim list and posts them in Slack for an admin to approve. It never sends a Grammarly invite, never removes a member, and never changes your seat count.
How does it decide a seat is idle?
By the activity shown in the Grammarly admin members view against the idle window you set, for example 30 or 60 days. Idle seats are listed for review, never revoked.
Does it read what my team has written?
No. WebRun reads only the admin members list: who holds a seat, their group, and whether it is active. Document content and individual writing suggestions are never opened.
Put this on autopilot.
Turn it on in minutes - or have our team set it up for you.