The Activation Requests screen lists pending and processed employee access requests at the routeDocumentation Index
Fetch the complete documentation index at: https://docs.encoreos.io/llms.txt
Use this file to discover all available pages before exploring further.
/settings/activation-requests.
Overview
The screen lists all activation requests scoped to the current organization from thepf_user_activation_requests table. Requests are split into a “Pending” section with Approve/Deny buttons and a “Processed” section showing resolved requests with their status badge. Approvals and denials are submitted via the pf_approve_activation_request and pf_deny_activation_request RPCs. Success and error feedback is shown via toast notifications.
Who it’s for
Required permission:system.organizations.admin
Before you start
- You must hold the
system.organizations.adminpermission. - Requests appear here when employees are imported or migrated and need manual org access approval.
Steps
Review pending requests
Examine each pending request showing the user’s name, email, and optional reason.
Key concepts
pf_user_activation_requests— table storing activation requests per organizationpf_profiles— joined to resolve user name and emailpf_approve_activation_request/pf_deny_activation_request— RPCs used for approval actions
Related
Platform Foundation
Platform Foundation overview.
Governance & parity
Documentation coverage and governance.
This page documents shipped product behavior. It is not medical, legal, or
billing advice. Verify against your organization’s policies and applicable
regulations before using it for clinical, compliance, or billing decisions.
Protected health information (PHI) shown in the product is governed by your
tenant’s access controls and is never exposed in this documentation.
Documentation sources
Documentation sources
- src/routes/platform.tsx
- src/platform/settings/ActivationRequestsPage.tsx