grammarly-enterprise-rbac

name	grammarly-enterprise-rbac
description	Configure Grammarly enterprise role-based access control. Use when managing team access, configuring organization settings, or implementing Grammarly enterprise governance. Trigger with phrases like "grammarly enterprise", "grammarly teams", "grammarly rbac", "grammarly organization", "grammarly admin".
allowed-tools	Read, Write, Grep
version	1.8.0
license	MIT
author	Jeremy Longshore <[e-mail]>
tags	["saas","grammarly","writing","enterprise"]
compatibility	Designed for Claude Code

Grammarly Enterprise RBAC

Overview

Grammarly enterprise deployments manage writing quality across teams with different access levels. Organization admins control style guides, tone profiles, and brand rules. Team admins assign seats and configure suggestion types (clarity, engagement, delivery). Members write with team defaults while guests get read-only access to shared documents. HIPAA and SOC 2 compliance in regulated industries require audit trails on who accessed which writing suggestions and AI detection results.

Role Hierarchy

Role	Permissions	Scope
Org Admin	Manage billing, SSO config, all style guides, API credentials	Organization-wide
Team Admin	Assign seats, configure suggestion settings, manage style guides	Own team
Member	Write with team settings, access scoring and AI detection APIs	Own team
Guest	View shared documents, read-only style guide access	Invited documents only
API Service	OAuth-scoped access to scoring, AI detection, plagiarism APIs	Per-credential scope

Permission Check

async function checkGrammarlyAccess(userId: string, team: string, scope: string): Promise<boolean> {
  const response = await fetch(`${GRAMMARLY_API}/organizations/${ORG_ID}/permissions`, {
    headers: { Authorization: `Bearer ${GRAMMARLY_OAUTH_TOKEN}`, 'Content-Type': 'application/json' },
  });
  const perms =  response.();
   userPerms = perms..( m. === userId);
   (!userPerms)  ;
   userPerms. === team && userPerms..(scope);
}