in this guide
Picture a 90-person company on a Tuesday afternoon. A project manager sends the office’s IT person a direct message: “can you add me to the finance drive? Need the Q3 numbers for the client deck.” The IT person knows her, is busy, and adds her to the finance group in under a minute. A thumbs-up closes the thread.
Nothing about that was wrong. She needed the numbers, and she got them fast. But look at what the company now holds. The admin console shows that she is in the finance group, which grants every folder the group can open. Its log shows that the IT person added her, on that date. The reason, the fact that nobody from finance agreed, and the unspoken “just for this deck” live in a chat thread.
where each part of a grant ends up
- 1the askA direct message to whoever has admin rights.
- 2the clickThe admin adds the person to a group or role.
- 3the splitThe log keeps who clicked. The chat keeps why, and for how long.
- 4the question months laterA review or a leaver asks why she has this. Nobody can show it.
This guide is about that moment of granting: the channel requests travel through, the record they leave, and the light request flows a company without a security team can actually run. It pairs with day one, already too much, which argues for moving default access to on-demand requests. On-demand only helps if the request leaves a trace.
what the log remembers, and for how long
Admin consoles record the grant. The request never passed through them, so they have nothing to say about it.
Google records the actor. Google’s help page on Groups Enterprise log events says the log shows when an administrator added a user, and that the Actor field is the email address of the person who performed the action. In the scenario above, the log says the IT person did it. It cannot say who asked or who agreed, because that happened somewhere else.
The click itself has a horizon. Google’s data retention page lists six months for Admin, Groups and Drive log events, and says admins cannot change that. Microsoft’s Entra data retention page lists seven days for audit logs on Entra ID Free and 30 days on P1 or P2. On a free Entra tenant, the record of who added someone to a group can be gone in a week unless it was exported. The guide on 12 March explains why history questions die with the log, and the log export guide is the routine that keeps them.
The chat has a horizon too. Slack’s plans page lists “90-day access” to message history on the Free plan, with a footnote that Free messages and files are kept for one year and older content is permanently deleted. Paid plans and other chat tools keep messages on their own schedules, which an admin may or may not have set.
The grant outlives every record of why it was made.
That is the gap. The access is state: anyone can see it today. The reason is history, and it was never written anywhere built to keep it.
three shortcuts that become the process
Each is what happens when granting access has no home.
The direct message to whoever has admin. The fastest route wins. The person with admin rights becomes the access desk, judges each request alone, and may be the person least placed to know whether finance data should go to a project manager. A request in chat also arrives with whatever identity the chat account shows; if that account is compromised, the request still reads as genuine.
The approval that is only a reply. Sometimes there is an approval: a manager writes “fine by me” in a thread. That is a real decision. It is also recorded in a place nobody will search at review time, against a resource described in loose words (“the finance drive”), with no end date.
Admin by default, for speed. When the request is “I keep needing you to change this setting”, the quickest answer is to make the person an admin. Microsoft’s own best-practice page for Entra roles warns against assigning broader roles at broader scopes “even if it initially seems more convenient”, recommends fewer than five Global Administrators, and notes that whoever signs up for a Microsoft cloud service gets the Global Administrator role by default. Speed-driven admin rights add to that starting point. The Twitter 2020 case shows what an internal admin tool held by many staff becomes once attackers talk their way into staff accounts. The stayers guide tells what happens to the “two weeks of admin” that nobody rolls back.
The common thread is a quick grant with no record behind it. The grant can stay just as quick; what has to change is that it leaves five facts behind.
the five facts a grant should leave
CIS Controls safeguard 6.1, part of the smallest implementation group, asks for a process, preferably automated, for granting access on a new hire, a rights grant or a role change. The CIS assessment specification checks whether that process exists and which of those cases it covers. It does not prescribe a tool. For a small company, a workable version is a record of five things for every grant beyond the default bundle:
- Who gets it. The person, by their account name.
- What exactly. The group, role or folder, at the narrowest level that works.
- Why. One line tied to work: the client, the project, the task.
- Who agreed. Someone who owns the data or the system, ideally a different person from the one who clicks.
- Until when. A date, or “ongoing, check at next review”.
the same grant, two different trails
granted in chat
what is left after a few months
- A group membership in the console
- A log entry naming the admin, until it expires
- A thread nobody will search, if it still exists
granted through a request
what is left after a few months
- Who, what, why, who agreed, until when
- An end date that removes it or prompts a check
- A record a reviewer or auditor can read
Those five facts are what make an access review possible. A reviewer who sees a reason and an end date can decide in seconds. A reviewer who sees only a name in a group has to guess or ask around, and the easiest answer to “does she still need this?” is to leave it.
request flows you may already own
Several tools a company already pays for include a request and approval flow. The features below are as each vendor documents them in November 2026. Plan requirements change, so check yours.
Google Groups join requests. When an access group is created, Google’s admin help lists three join options, one of which lets anyone in the organization ask to join. Google Groups help says the group owner, or anyone with permission to manage members, sees requests under Pending members and accepts or denies each one. If folders, shared drives and app access are granted to groups, the group owner becomes the approver, and the request lands with someone who knows the data. The why still needs a place: a request note or a line in a shared sheet.
Microsoft Entra self-service groups. Microsoft’s documentation says group owners can approve or deny membership requests in the My Groups portal, and that requesting to join and approving both need Entra ID P1 or P2. The same page lists Microsoft 365 groups as open for any user to join by default when created in My Groups, the Azure portal or PowerShell, so check the setting on groups that grant anything sensitive.
Microsoft Entra access packages. Entitlement management bundles groups, apps and SharePoint sites into an access package with a policy that sets who can request, who approves and when access expires. Microsoft’s approval settings page includes a switch to require a justification from the requester, the manager as an approver with a fallback, and a deadline after which an unanswered request is denied automatically. The reports page lists audit records for each request, approval, fulfilment and removal, and a drift report in preview that lists access granted outside the access package policies. Microsoft says this needs Entra ID Governance or Entra Suite.
Microsoft Entra Privileged Identity Management for admin roles. PIM makes a person eligible for a role, then has them activate it for a limited time with a justification, and optionally an approval and MFA. Microsoft lists P2 or ID Governance as the requirement. It answers admin-by-default: the admin right exists only while someone is using it, and the activation records why.
Okta Access Requests. Okta’s help centre describes requests for apps, groups and entitlement bundles, routed through approval sequences, with requesters able to use Slack, Microsoft Teams or the web. A Past Access Requests report shows who asked, whether access was granted and by whom. Okta documents it under Identity Governance; confirm what your plan includes.
Nothing licensed at all. A form or a ticket queue that writes the five facts into one sheet, plus a rule that admins grant only from that sheet, works on any plan. It keeps the speed of chat if the form is a link people can open from chat.
Whatever the tool, the record exists before the click.
keep admin rights out of the request path
Two changes stop the admin shortcut without slowing anyone down.
Separate the admin account from the daily one. A person who needs admin to change settings once a month signs in to an admin account for that and works the rest of the time without it. The emergency account guide covers the account that sits outside this rule on purpose.
Grant the role that fits the task. Microsoft’s Entra best-practice page points to narrower built-in roles, custom roles and administrative units that limit a role to part of the directory. A request for “admin” can sometimes be met with a smaller role that covers the actual task.
The test of the record is the question a customer’s security questionnaire or an auditor eventually asks: show how access to this system was approved. A row with five facts and a date answers it. A thread, if it can still be found, leaves the reader to reconstruct the decision.
When did someone last ask you for access in a chat message, and could you find that message today?
sources
- Google Workspace Help: Groups Enterprise log events
- Google Workspace Help: Data retention and lag times
- Google Workspace Help: Create a group in your organization
- Google Groups Help: Add people to your group
- Microsoft Learn: Microsoft Entra data retention
- Microsoft Learn: Set up self-service group management in Microsoft Entra ID
- Microsoft Learn: What is entitlement management?
- Microsoft Learn: Change approval settings for an access package in entitlement management
- Microsoft Learn: View reports and logs in entitlement management
- Microsoft Learn: What is Privileged Identity Management?
- Microsoft Learn: Best practices for Microsoft Entra roles
- Okta Help Center: Access Requests overview
- Okta Help Center: Get started with Access Requests
- CIS Controls Assessment Specification: 6.1 Establish an Access Granting Process
- Slack Help Center: Slack plans and features
