Skip to content
Docs

Suggested searches

    Search all documentation ↑↓ to navigate Enter to open Esc to close

    Get compliant

    Permissions and integrations

    Control who can read and manage Compliance Portals, connect access notifications to Slack, and automate portal workflows through OAuth, CLI, MCP, or n8n.

    Markdown

    Compliance Portal administration follows the person’s organization role and the organization boundary.

    Console permissions

    Section titled “Console permissions”
    • Owners and admins have full Compliance Portal management access for their organization. They can create, update, activate, and delete portals; manage published content and access; send updates; and configure custom domains.
    • Viewers have read-only access to portal settings, visitor access, files, references, commitments, frameworks, custom links, and domains.
    • Managed domains cannot be deleted through the custom-domain delete permission.
    • Auditor and employee roles do not receive the Compliance Portal management policies.

    Use the least-privileged role that fits the person’s work. See Roles and permissions for organization-wide role guidance.

    Slack

    Section titled “Slack”

    Send access requests to a Slack channel so reviewers can approve them without opening the console.

    1. Open Settings → Integrations.
    2. If the Probo Slack app is not installed yet, select Install, choose your Slack workspace, and select Allow.
    3. Under Slack notifications, choose the channel where access requests should land, such as #access-requests.
    4. Ask every reviewer to run /probot login in Slack to link their Slack account to their Probo account.

    Reviewers who have not run /probot login still see requests in the channel, but they cannot approve or reject them until their account is linked.

    Connecting or changing the channel requires permission to initiate connectors. A connection without a selected channel is shown as not configured.

    API and automation access

    Section titled “API and automation access”

    OAuth clients can request one of two Compliance Portal scopes:

    • v1:compliance-page:read grants portal read operations, including lists of access records, files, references, mailing-list updates and subscribers, frameworks, links, domains, and commitments.
    • v1:compliance-page adds create, update, delete, access-management, mailing-list, domain, and publishing operations.

    The caller must still be authorized for the target organization. Keep credentials out of workflows and grant write access only where an automation must change portal state.

    Use the supported interface for the job:

    Rights-request automation is documented separately in the CLI, MCP privacy catalog, and n8n references.

    To notify another system when a portal visitor creates or changes a rights request, subscribe to the corresponding webhook events.