Access requests
Overview
Section titled “Overview”Access requests capture people who tried to join your workspace on their own, for example by opening a join link or entering your workspace URL, without an existing invite. Instead of letting them in automatically, GrowthOS queues the request for an Owner or Admin to review.
Every request shows the requester email, the time of the request, and any context they provided, so you can make an informed decision instead of approving blind. Approving a request is functionally equivalent to sending an invite: you still choose the role and seat type at approval time.
Until a request is approved, the requester sees an access-pending screen instead of the workspace. This is expected behavior, not an error, and resolves as soon as an Admin acts on the request.
What you can do here
Section titled “What you can do here”- See a queue of everyone who has requested to join your workspace.
- Review the requester email and any context before deciding.
- Approve a request with a chosen role and seat type.
- Reject a request that should not get access.
- Track how long a request has been waiting.
When to use
Section titled “When to use”- Someone messages you saying they are stuck on an access-pending screen.
- Reviewing workspace access on a regular cadence for security hygiene.
- Onboarding new members who found the workspace on their own rather than through a direct invite.
Prerequisites
Section titled “Prerequisites”- Owner or Admin role to approve or reject requests.
- A workspace configured to require approval for self-requested access.
Where to find it
Section titled “Where to find it”- Sidebar: Organization → Access requests
- Direct route:
/org/access-requests
Step-by-step
Section titled “Step-by-step”- Open Organization → Access requests (
/org/access-requests). - Review the queue of pending requests.
- Open a request to see the requester email and any provided context.
- Decide whether the person should have access to this workspace.
- Approve with a chosen role and seat type, or reject the request.
- Confirm with the requester that they can now sign in successfully.
What success looks like
Section titled “What success looks like”- No legitimate request sits unresolved for more than a day or two.
- Every approved request lands with the correct role and seat, not a default guess.
- Requesters who message you about being stuck get resolved quickly from this one queue.
Tips & best practices
Section titled “Tips & best practices”- Check this queue whenever someone reports being stuck on access-pending; it is almost always the fix.
- Reject requests you do not recognize rather than leaving them pending indefinitely.
- Approve with the same care you would use when sending a direct invite; the access level is identical.
Common mistakes
Section titled “Common mistakes”- Assuming self-requested access is automatically granted; it always waits for Admin review by design.
- Leaving requests pending for days, which looks like a broken product to the requester.
- Approving a request without checking who it actually is, granting access to the wrong person.