# Orbiq Trust Center Documentation > Full text of all 217 Orbiq Trust Center documentation pages. > Index of the same pages: https://docs.orbiqhq.com/llms.txt # MCP Server Source: https://docs.orbiqhq.com/docs/mcp Connect Claude, Cursor, or any MCP client to the Orbiq Trust Center documentation for live search and full API reference access # MCP Server [#mcp-server] The Orbiq documentation is available as a [Model Context Protocol](https://modelcontextprotocol.io) server, so AI assistants can search these docs and read the full Admin Center API reference without you copying anything into a chat window. The server is public, read-only, and needs no authentication. ``` https://docs.orbiqhq.com/mcp ``` It speaks Streamable HTTP. There is no stdio transport and no API key to provision. ## Setup [#setup] ```bash claude mcp add --transport http orbiq-docs https://docs.orbiqhq.com/mcp ``` Add to `~/.codex/config.toml`: ```toml [mcp_servers.orbiq-docs] url = "https://docs.orbiqhq.com/mcp" ``` Codex talks to Streamable HTTP servers directly, so no local bridge is needed. Add to `claude_desktop_config.json`: ```json { "mcpServers": { "orbiq-docs": { "type": "http", "url": "https://docs.orbiqhq.com/mcp" } } } ``` Add to `.cursor/mcp.json` in your project, or to `~/.cursor/mcp.json` globally: ```json { "mcpServers": { "orbiq-docs": { "type": "http", "url": "https://docs.orbiqhq.com/mcp" } } } ``` Add to `.vscode/mcp.json`: ```json { "servers": { "orbiq-docs": { "type": "http", "url": "https://docs.orbiqhq.com/mcp" } } } ``` ## Tools [#tools] | Tool | Purpose | | ---------------- | -------------------------------------------------------------------------------------------------------- | | `search_docs` | Full-text search across every page, including the API reference. Returns titles and URLs. | | `get_page` | Fetch one page as Markdown. API pages expand into parameters, request body, responses, and code samples. | | `list_endpoints` | Every REST operation with its method, route and summary. Pass a `tag` to see one resource at a time. | | `list_guides` | Nested index of the product guides. REST operations are in `list_endpoints`, not here. | Ask in whichever language you work in. Questions are translated to search the documentation, which is written in English, and the assistant answers in the language you used. ## Example prompts [#example-prompts] Once connected, ask your assistant things like: * "Using the Orbiq docs, how do I create a customer account through the API?" * "What fields does the access request webhook send?" * "Write me a script that uploads a document and activates a new version." ## Without MCP [#without-mcp] If your tooling does not speak MCP, the same content is available as plain files: | Resource | URL | | --------------------------- | ---------------------------------------------------------- | | Index of all pages | [`/llms.txt`](https://docs.orbiqhq.com/llms.txt) | | Full corpus in one file | [`/llms-full.txt`](https://docs.orbiqhq.com/llms-full.txt) | | Any single page as Markdown | append `.md` to its URL | Requests sending `Accept: text/markdown` receive Markdown from the normal page URL, so no rewriting is needed. ## Related [#related] * [Admin Center API](/docs/api) — what the API itself can do * [API v1 Reference](/docs/api/v1) — every endpoint, generated from OpenAPI --- # User Guide Source: https://docs.orbiqhq.com/docs/user-guide Complete guide to using the Trust Center Admin interface for managing customer accounts, documents, certifications, and compliance workflows # Admin Center User Guide [#admin-center-user-guide] Welcome to the comprehensive user guide for the Trust Center Admin Center! This documentation will help you master every aspect of managing your compliance and trust center operations. ## Quick Start [#quick-start] New to the Admin Center? Start here for the essential basics Sign in, accept invitations, and reset passwords securely Learn how to create and manage customer accounts Upload, organize, and control access to compliance documents ## Core Features [#core-features] ### Account Management [#account-management] Manage your customer organizations and their compliance journey. View and manage all customer accounts in one place Set up new customer accounts with proper configuration Configure account details, contacts, and access settings Manage document access and permissions per account ### Document Management [#document-management] Control your compliance documents and access permissions. Browse and manage your complete document library Add new documents with proper categorization Use templates to streamline document creation Configure who can access which documents ### Trust Center Layout [#trust-center-layout] Design custom layouts and content experiences for your Trust Center. Build bespoke Trust Center tabs with custom layouts and content blocks ### Updates [#updates] Publish Trust Center updates and notify subscribed customers. Create, schedule, share, and manage customer-facing update timelines ### Certifications [#certifications] Manage compliance certificates with validity tracking. View and manage all your compliance certifications Create and configure new certifications Use predefined templates for common certifications ### Subprocessors [#subprocessors] Publish and maintain your vendor register. Understand how vendor records connect the admin center and Trust Center. Capture vendor identity, processing locations, and Markdown usage details. Update badge assets, adjust usage summaries, or remove vendors. ### User Management [#user-management] Handle user invitations, roles, and permissions. Manage all users and their access levels Add new team members to your admin center Configure role-based access controls ## Configuration & Customization [#configuration--customization] ### Brand Management [#brand-management] Configure your white-label themes and trust center appearance. Customize colors, logos, and overall appearance Upload and manage your brand logos Configure colors and styling options ### Integrations [#integrations] Set up API keys and external integrations. View and manage all your integrations Generate and manage API access credentials ### Knowledge Base [#knowledge-base] Manage Q\&A content for customer self-service. Create and manage Q\&A content for customers Add, edit, and organize frequently asked questions ## Analytics & Insights [#analytics--insights] ### Analytics Dashboard [#analytics-dashboard] Track user interactions and system usage. View detailed analytics and usage metrics ## Advanced Features [#advanced-features] ### API Configuration [#api-configuration] Configure API endpoints and technical settings. Configure API endpoints and technical settings ### Features [#features] Manage advanced features and capabilities. Tailor Trust Center content for different customer audiences Enable and configure advanced features ## Getting Help [#getting-help] **Need assistance?** Each guide includes step-by-step instructions, screenshots, and troubleshooting tips to help you succeed. Technical documentation for developers Contact support and find additional resources *** Ready to get started? Choose a topic above or start with our [Getting Started guide](/docs/user-guide/login) for the essential basics. --- # Admin Center API Source: https://docs.orbiqhq.com/docs/api Complete REST API reference for building and managing powerful white-label trust centers # Trust Center Admin API [#trust-center-admin-api] Build powerful white-label trust center with our comprehensive REST API. The Trust Center Admin API enables you to programmatically manage customer accounts, documents, certifications, access requests, and branded trust center configurations at enterprise scale. ## What You Can Build [#what-you-can-build] Create customer accounts, invite contacts, and provision document access through automated workflows and integrations. Upload compliance documents, manage access levels, handle access requests, and automate approval processes. Track certifications, manage NDA workflows, automate access approvals, and maintain compliance audit trails. Configure branded trust centers, manage deployment domains, and customize the complete customer experience. ## Why Choose Our API [#why-choose-our-api] ### 🚀 **REST-First Design** [#-rest-first-design] Built following industry best practices from Stripe, GitHub, and Notion. Clean HTTP endpoints, predictable resource patterns, and comprehensive error handling designed for seamless integration. ### 🔒 **Enterprise Security** [#-enterprise-security] API key authentication, role-based access control, tenant isolation, and comprehensive audit logging. Designed for enterprise compliance requirements. ### ⚡ **Production Ready** [#-production-ready] Rate limiting, automated notifications, and 99.5% uptime SLA. Scale from prototype to enterprise without architectural changes. ## Getting Started [#getting-started] ### 1. Authentication [#1-authentication] The Admin Center API uses API keys for programmatic access. Browser login is available only through the Admin Center UI and does not issue API bearer tokens. Create an API key from **Admin Center → Integrations → API Keys**, store it securely, and pass it as a bearer token: ```bash Authorization: Bearer $TRUST_CENTER_API_KEY ``` **Use API keys for:** * Production server-to-server integrations * Automated compliance workflows * Long-running background processes * CI/CD pipelines and deployment scripts ### 2. Your First API Call [#2-your-first-api-call] Test your setup by listing customer accounts in your tenant: ```bash curl -H "Authorization: Bearer $TRUST_CENTER_API_KEY" \ -H "Content-Type: application/json" \ https://app.orbiqhq.com/api/v1/accounts ``` ```javascript const response = await fetch("https://app.orbiqhq.com/api/v1/accounts", { headers: { Authorization: "Bearer " + apiKey, "Content-Type": "application/json", }, }); const { accounts } = await response.json(); console.log(`Managing ${accounts.length} customer accounts`); ``` ### 3. Explore the Documentation [#3-explore-the-documentation] Complete endpoint documentation with HTTP examples and schemas Learn about JWT tokens, session management, and security best practices ## API Capabilities Overview [#api-capabilities-overview] ### **Core Resource Management** [#core-resource-management] * **Accounts** - Manage customer organizations, contacts, and compliance workflows * **Users** - Handle user invitations, roles, and profile management * **Documents** - Upload, categorize, and control access to compliance documents * **Certifications** - Manage certificates with validity tracking and automated renewals * **Frequently Asked Questions** - Manage Q\&A content for making your trust center more understandable * **Knowledge Base** - Manage Q\&A content for customer self-service search ### **Workflow Automation** [#workflow-automation] * **Access Requests** - Handle trust center visitor requests and automated approvals * **Notifications** - Send/Receive template-based emails, webhooks or Slack/Teams messages for onboarding and approvals * **Analytics Tracking** - Monitor user interactions and system usage patterns * **Brand Management** - Configure white-label themes and deployment settings ### **Enterprise Administration** [#enterprise-administration] * **API Key Management** - Generate and manage programmatic access credentials ## Enterprise Features [#enterprise-features] ### **White-Label Capabilities** [#white-label-capabilities] * Custom domain deployment (trust.yourcompany.com) - Available in non-free plans * Complete brand customization (logos, colors, fonts) * No trace of Orbiq in customer-facing interfaces * Multi-language support (EN/DE/FR) ### **Compliance & Security** [#compliance--security] * SOC 2 Type II certified infrastructure * GDPR and data residency compliance * Comprehensive audit logs for all operations * Role-based access control with tenant isolation ### **Scale & Performance** [#scale--performance] * European CDN for global file delivery * Auto-scaling infrastructure * Sub-200ms API response times (p95) * 99.9% uptime SLA with real-time status monitoring ## Real-World Integration Examples [#real-world-integration-examples] ### **Automated Customer Onboarding** [#automated-customer-onboarding] ```bash # 1. Create customer account with contacts curl -X POST "https://app.orbiqhq.com/api/v1/accounts" \ -H "Authorization: Bearer $TOKEN" \ -H "Content-Type: application/json" \ -d '{ "title": "Acme Europe", "description": "Fictional company compliance management", "contacts": [ { "email": "compliance@acme.example", "first_name": "Jane", "last_name": "Smith", "title": "Compliance Manager" } ] }' # 2. Share relevant compliance documents curl -X PATCH "https://app.orbiqhq.com/api/v1/accounts/acc_123/documents" \ -H "Authorization: Bearer $TOKEN" \ -H "Content-Type: application/json" \ -d '{ "document_ids": ["doc_privacy_policy", "doc_security_audit"], "access_level": "restricted" }' ``` ### **Access Request Approval Workflow** [#access-request-approval-workflow] ```bash # 1. List pending access requests curl -H "Authorization: Bearer $TOKEN" \ "https://app.orbiqhq.com/api/v1/access-requests?review_status=to_review" # 2. Approve access request (triggers automatic email) curl -X PATCH "https://app.orbiqhq.com/api/v1/access-requests/req_123" \ -H "Authorization: Bearer $TOKEN" \ -H "Content-Type: application/json" \ -d '{"review_status": "approved"}' ``` ### **Brand Configuration for White-Label Trust Centers** [#brand-configuration-for-white-label-trust-centers] ```bash # Configure trust center appearance curl -X PATCH "https://app.orbiqhq.com/api/v1/brand" \ -H "Authorization: Bearer $TOKEN" \ -H "Content-Type: application/json" \ -d '{ "title": "Acme Trust Center", "primary_color": "#0066cc", "deployment_domains": "trust.acme.com,trust.acme.de", "footer_text": "© 2025 Acme. All rights reserved." }' # Upload custom logo curl -X PUT "https://app.orbiqhq.com/api/v1/brand/logo" \ -H "Authorization: Bearer $TOKEN" \ -H "Content-Type: multipart/form-data" \ -F "file=@/path/to/company-logo.png" ``` ### **Document Management Integration** [#document-management-integration] ```bash # 1. Create document metadata. `category` is the UUID of an existing category, # not its name, and `featured` selects where the document is highlighted. curl -X POST "https://app.orbiqhq.com/api/v1/documents" \ -H "Authorization: Bearer $TOKEN" \ -H "Content-Type: application/json" \ -d '{ "title": "SOC 2 Type II Report", "description": "Annual security audit report", "access_level": "requires_nda", "category": "550e8400-e29b-41d4-a716-446655440000", "featured": { "control": true, "resource": false } }' # 2. Upload the file to the document the first call returned curl -X PUT "https://app.orbiqhq.com/api/v1/documents/$DOCUMENT_ID/file" \ -H "Authorization: Bearer $TOKEN" \ -H "X-Original-Filename: soc2-report.pdf" \ --data-binary @soc2-report.pdf ``` ## HTTP Status Codes & Error Handling [#http-status-codes--error-handling] ### Standard Response Codes [#standard-response-codes] | Code | Meaning | Usage | | ----- | ----------------- | ----------------------------------------------- | | `200` | OK | Successful GET/PATCH operations | | `201` | Created | Successful POST operations | | `204` | No Content | Successful DELETE operations | | `400` | Bad Request | Invalid request parameters or validation errors | | `401` | Unauthorized | Missing or invalid authentication token | | `403` | Forbidden | Insufficient permissions for the operation | | `404` | Not Found | Requested resource does not exist | | `409` | Conflict | Resource conflict (e.g., duplicate email) | | `429` | Too Many Requests | Rate limit exceeded | | `500` | Server Error | Unexpected server error | ### Error Response Format [#error-response-format] ```json { "error": { "type": "validation_error", "message": "Invalid email address format", "param": "email" } } ``` ## Rate Limits & Best Practices [#rate-limits--best-practices] * **Rate Limit**: 1000 requests per minute per authentication token * **Bulk Operations**: Use bulk endpoints for managing multiple resources * **Error Handling**: Implement exponential backoff for rate limit and server errors ## Integration Patterns [#integration-patterns] ### **Webhook Notifications** [#webhook-notifications] Set up real-time notifications for account events, document uploads, and access request status changes. ### **Batch Processing** [#batch-processing] Use bulk endpoints for processing large datasets efficiently. ### **Multi-Tenant Architecture** [#multi-tenant-architecture] Each API token is automatically scoped to your tenant - no need to specify tenant IDs in requests. *** Ready to get started? Head to the [API v1 Reference](/docs/api/v1) for detailed endpoint documentation and HTTP examples. --- # Custom Fields in Access Requests Source: https://docs.orbiqhq.com/docs/user-guide/access-requests/custom-fields How the Trust Center collects custom fields during access requests and how required fields are handled. # Custom Fields in Access Requests [#custom-fields-in-access-requests] This guide explains how custom fields are shown to visitors, how required fields are enforced, and how we try to auto-fill missing details using safe web search. ## What shows up in the modal [#what-shows-up-in-the-modal] * **Always ask** fields are shown in the request modal immediately. Required ones must be filled before submit. * **Non–always ask** fields stay hidden. We first try to gather them automatically (see below). If any required ones are still missing, we’ll prompt the visitor for those specific fields in a second step. * Fields can target either **contacts** or **accounts**. We route answers to the right collection automatically. * Select and multi-select fields are displayed with your localized option labels. ## Auto-filling hidden required fields [#auto-filling-hidden-required-fields] We attempt a lightweight web search based on the visitor’s email domain to pre-fill hidden required fields (for example company region or segment). This only runs for required fields that are not marked `always_ask`. We never send the visitor’s email to the search—only the domain is used. If the search doesn’t return values for those required fields, the visitor sees a secondary prompt to provide them manually before the request is accepted. ## Persistence rules [#persistence-rules] * Custom field answers are stored when a **new account** is created from the request. Existing accounts/contacts are not updated. * Answers are attached to the collection defined on the template (`accounts` or `contacts`). * Required validation happens server-side. Missing required fields will block submission until provided (either upfront or after the secondary prompt). ## Visitor flow summary [#visitor-flow-summary] Visitor fills the modal with email, selected documents, and any **always ask** custom fields. We try to auto-fill hidden required fields via domain-based web search. If any hidden required fields remain, the visitor is prompted to provide them before the request is accepted. For new accounts, provided custom fields are stored alongside the account/contact and the access request proceeds. ## FAQs [#faqs] * **Can we skip the web search step?** Yes—set fields to `always_ask` to collect them directly in the modal. * **Do we ever update existing records?** No. Custom fields are only attached when a new account/contact is created from the request. * **How are languages handled?** Field titles and option labels honor your translations; we fall back to English when needed. --- # Access Request Management Source: https://docs.orbiqhq.com/docs/user-guide/access-requests Learn how to manage document access requests through an intuitive kanban board interface # Access Request Management [#access-request-management] Access requests are created when contacts request access to your Trust Center documents. The kanban board interface helps you efficiently review and process these requests through different stages. ## What You'll Learn [#what-youll-learn] * Understanding the access request workflow * Using the kanban board interface * Processing requests efficiently * Automatic approval workflows * Magic link email system ## Prerequisites [#prerequisites] * Admin or Account Manager role * Contacts created in the system * Documents available for sharing * Email service configured for magic links ## Access Request Overview [#access-request-overview] Access requests track when external users want to view your compliance documents. Each request contains: * Contact information (name, email, company) * Requested documents list * Current review status * Request timeline 💡 **Automatic Creation**: Access requests are automatically created when someone submits a request through your Trust Center's public interface. ## Kanban Board Interface [#kanban-board-interface] The access requests page uses a visual kanban board with four columns: New requests awaiting initial review Requests currently being evaluated Completed requests with access granted Requests that were denied ### Board Features [#board-features] * **Drag and Drop**: Move cards between columns to change status * **Quick View**: Click cards to see full details * **Bulk Actions**: Select multiple requests for batch processing * **Real-time Updates**: Changes sync automatically * **Search and Filter**: Find specific requests quickly ## Processing Access Requests [#processing-access-requests] ### Review Workflow [#review-workflow] **Initial Review** - Check contact's email domain - Verify against approved accounts - Review requested documents **Move to In Review** - Drag card to "In Review" column - Indicates active evaluation - Sends status update to contact **Make Decision** - Approve: Grant access to documents - Reject: Deny the request - Request Info: Ask for clarification **Complete Request** - Drag to final column - Triggers appropriate actions - Updates contact status ### Approval Process [#approval-process] When approving an access request: 1. **Status Update** - Request moves to "Approved" 2. **Magic Link Generation** - Secure access link created 3. **Email Notification** - Link sent to contact 4. **Document Access** - Contact can view shared documents 5. **Audit Trail** - Activity logged for compliance ✅ **Magic Links**: Approved contacts receive a secure magic link via email that expires after 24 hours (configurable). The link provides direct access to their approved documents. ## Request Card Details [#request-card-details] Each request card displays: ### Contact Information [#contact-information] * Full name with status icon * Email address * Job title (if provided) * Company name ### Request Details [#request-details] * Documents requested (up to 3 shown) * Total document count if more * Request date * Last update timestamp ### Visual Indicators [#visual-indicators] * **Contact Status Icons**: * 🕐 To Review (yellow) * 👁 In Review (blue) * ✅ Approved (green) * ❌ Rejected (red) * 🚫 Cancelled (gray) ## Advanced Features [#advanced-features] ### Contact Status Sync [#contact-status-sync] When processing requests, you can optionally update the contact's status: If the contact is new or pending: - Prompt appears to approve contact too - Single action approves both request and contact - Streamlines the approval process For existing contacts: - Only the request status changes - Contact status remains independent - Useful for restricted document requests ### Auto-Approval Integration [#auto-approval-integration] Access requests integrate with the document sharing system: 1. When documents are shared via contact management 2. If all requested documents are shared 3. The related access request auto-approves 4. Magic link email sends automatically 💡 **Efficiency Tip**: Use the contact's Documents tab to share multiple documents at once, which can auto-approve pending requests. ## Search and Filtering [#search-and-filtering] ### Search Functionality [#search-functionality] * Search by contact name * Search by email address * Search by company name * Real-time results as you type ### Filter Options [#filter-options] * Filter by review status * Filter by account * Filter by date range * Combine multiple filters ## Trust Center User Experience [#trust-center-user-experience] From the Trust Center visitor's perspective: **Request Submission** - Visitor fills out access request form - Selects desired documents - Provides contact information **Confirmation** - Receives confirmation message - Told to expect email when approved - Can check status with request ID **Approval Email** - Receives magic link email - Link valid for 24 hours - One-click access to documents **Document Access** - Lands on personalized portal - Sees approved documents * Can download/view as permitted ## Best Practices [#best-practices] Review new requests within 24 hours to maintain good customer experience Establish clear approval criteria and document them for team consistency Process similar requests together for efficiency ### Approval Guidelines [#approval-guidelines] Consider these factors when reviewing: * **Account Status** - Is their company approved? * **Email Domain** - Does it match the account? * **Document Sensitivity** - Are they requesting appropriate documents? * **Compliance Requirements** - Any regulatory considerations? ## Common Workflows [#common-workflows] ### New Customer Onboarding [#new-customer-onboarding] 1. Customer submits access request 2. Create/verify their account 3. Approve both account and contact 4. Share standard document package 5. Send welcome email with access ### Existing Customer Updates [#existing-customer-updates] 1. Known contact requests new documents 2. Verify they should have access 3. Quick approval through kanban 4. Documents automatically available ### Suspicious Requests [#suspicious-requests] 1. Unknown domain or suspicious email 2. Move to "In Review" for investigation 3. Verify through external channels 4. Reject if cannot authenticate ## Troubleshooting [#troubleshooting] **Common causes**: - Email service not configured - Invalid email address - Contact status not approved - Check email service logs **Solutions**: - Refresh the page - Check your permissions - Verify browser compatibility - Clear browser cache **Check**: - Documents actually shared with contact - Contact status is approved - Account status is approved - Document access levels ## Integration Points [#integration-points] ### With Contact Management [#with-contact-management] * Requests create contacts automatically * Contact status affects request processing * Document sharing triggers auto-approval ### With Document System [#with-document-system] * Request shows which documents wanted * Approval doesn't auto-share documents * Manual sharing still required ### With Email Service [#with-email-service] * Magic links sent on approval * Customizable email templates * Multi-language support ## Next Steps [#next-steps] Learn to manage contacts and their document access Configure documents for access requests Automate request processing via API ## Related Resources [#related-resources] * [Access Requests API Reference](/docs/api/v1/access-requests/get) * [Email Templates](/docs/user-guide/email-templates) --- # Trust Center Access Request Experience Source: https://docs.orbiqhq.com/docs/user-guide/access-requests/trust-center-experience What visitors see when they request access to restricted Trust Center content # Trust Center Access Request Experience [#trust-center-access-request-experience] This page describes the actual request flow implemented in the Trust Center app. ## What Visitors See [#what-visitors-see] Visitors can browse public content immediately. When they try to open a gated document, they are prompted to request access. Depending on your tenant configuration, the request modal can collect: * Email address * One or more requested documents * Tenant-defined custom fields shown in the request form ## Possible Outcomes [#possible-outcomes] The request flow returns one of three states: * `email_sent` * `pending_review` * `rejected` ## Auto-Approved Requests [#auto-approved-requests] If the requester already has the required access, or their account/domain is eligible for auto-approval, the system sends a magic link immediately. The Trust Center UI tells visitors that the magic link expires in **20 minutes**. ## Pending Review [#pending-review] If the requester is not already approved for the requested content, the request is stored for review in **Access Requests**. Account managers can approve or reject it from Admin Center. ## Email Domain Checks [#email-domain-checks] Before an access request is accepted, the Trust Center checks whether the requester's email domain looks safe and reachable. Requests are blocked when the email domain appears to be: * A disposable or temporary email provider * Unable to receive email, for example because required mail routing records are missing * Flagged by a high-risk email reputation signal * A high-risk free email provider result A domain with only an email authentication policy issue is not blocked. This is reported as a DMARC issue, and it usually means the domain's anti-spoofing policy is missing or incomplete. The domain can still receive magic link emails. If that authentication policy issue appears together with another blocking signal, the other signal still applies. For example, a domain with both a DMARC issue and missing mail routing records is blocked because magic links may not be deliverable. ## Rejected Requests [#rejected-requests] Rejected contacts are told that access was not approved. ## NDA-Protected Content [#nda-protected-content] If the requested document or entry requires an NDA, approval alone is not enough. The visitor must still complete the NDA flow before the restricted content becomes available. ## Related Docs [#related-docs] * [Access requests](/docs/user-guide/access-requests) * [NDA templates](/docs/user-guide/nda-templates) * [Email templates](/docs/user-guide/email-templates) --- # Account Document Access Source: https://docs.orbiqhq.com/docs/user-guide/accounts/account-documents Manage document permissions and access control for customer accounts in the Trust Center # Account Document Access [#account-document-access] Document access management is a critical component of Trust Center operations. This guide covers how to control which documents each account can access, ensuring proper security and compliance while providing customers with the resources they need. ## What You'll Learn [#what-youll-learn] * Understanding document access levels and permissions * How to assign documents to accounts * Managing bulk document permissions * Monitoring document access and usage * Troubleshooting access issues ## Prerequisites [#prerequisites] * **Admin** or **Account Manager** role required * Existing customer account * Documents uploaded to the Trust Center * Understanding of your organization's access policies ## Understanding Document Access Levels [#understanding-document-access-levels] ### Public Documents [#public-documents] **Characteristics:** * Automatically accessible to all accounts * No explicit permission required * Visible in all Trust Centers * Cannot be restricted per account **Use Cases:** * Company policies and procedures * General compliance statements * Public certifications and badges * Marketing and informational content ### Protected Documents [#protected-documents] **Characteristics:** * Require explicit permission assignment * Account-specific access control * Can be granted or revoked individually * Most common document type for compliance **Use Cases:** * Customer-specific agreements * Confidential compliance reports * Restricted certifications * Sensitive operational documents ### Internal Documents [#internal-documents] **Characteristics:** * Highly restricted access * Typically for specific accounts only * Require admin-level approval * Often contain sensitive information **Use Cases:** * NDA-protected documents * Account-specific assessments * Confidential audit reports * Restricted technical documentation Document Access Levels *Visual representation of the three document access levels* ## Accessing Document Management [#accessing-document-management] ### Navigation to Documents Tab [#navigation-to-documents-tab] 1. **Open Account Details**: Click on an account from the accounts list 2. **Navigate to Documents Tab**: Click the "Documents" tab in the account interface 3. **View Current Permissions**: See all documents and their current access status Documents Tab Navigation *Location of the Documents tab in the account management interface* ### Document List Interface [#document-list-interface] The documents interface shows: * **All Available Documents**: Complete list of Trust Center documents * **Current Access Status**: Whether the account has access to each document * **Document Details**: Title, category, and access level * **Bulk Selection**: Checkboxes for managing multiple documents Document List Interface *Complete document management interface with access indicators* ## Granting Document Access [#granting-document-access] ### Individual Document Assignment [#individual-document-assignment] **Step-by-Step Process:** 1. **Locate Document**: Find the document in the list 2. **Check Access Box**: Click the checkbox next to the document name 3. **Verify Selection**: Confirm the document shows as "granted" 4. **Save Changes**: Click "Save" or "Update Permissions" Individual Document Grant *Granting access to a single document* ### Bulk Document Assignment [#bulk-document-assignment] **For Multiple Documents:** 1. **Select Documents**: Use checkboxes to select multiple documents 2. **Choose Access Level**: Select appropriate permission level 3. **Apply to Selected**: Use "Grant Access to Selected" button 4. **Confirm Changes**: Review and save the permission updates Bulk Document Assignment *Bulk assignment of document access permissions* ### Category-Based Assignment [#category-based-assignment] **Assigning by Document Categories:** * **Compliance Documents**: Standard compliance reports and certifications * **Legal Documents**: Contracts, agreements, and legal notices * **Technical Documents**: Implementation guides and technical specifications * **Security Documents**: Security assessments and audit reports 💡 **Efficiency Tip**: Use category filtering to quickly assign all documents of a specific type to accounts that need them. ## Managing Document Permissions [#managing-document-permissions] ### Access Level Configuration [#access-level-configuration] **View-Only Access:** * Account can view document content * Cannot download or print * Suitable for reference materials * Tracking and analytics included **Download Access:** * Full view and download permissions * Account can save copies locally * Appropriate for implementation documents * Consider data security implications **Time-Limited Access:** * Access expires after specified period * Useful for temporary permissions * Automatic revocation on expiry * Good for project-based access Permission Configuration *Different access level options and their configurations* ### Permission Inheritance [#permission-inheritance] **Account-Level Defaults:** * Set default permissions for new documents * Apply standard access patterns * Reduce manual configuration * Ensure consistency across accounts **Document Category Rules:** * Automatic permissions based on document type * Streamline access management * Reduce administrative overhead * Maintain security standards ## Revoking Document Access [#revoking-document-access] ### Individual Access Removal [#individual-access-removal] **Process for Removing Access:** 1. **Locate Document**: Find the document with current access 2. **Uncheck Access Box**: Click to remove the checkmark 3. **Confirm Removal**: Verify the access change 4. **Save Changes**: Update the permissions immediately ⚠️ **Immediate Effect**: Access removal takes effect immediately and may interrupt active user sessions. ### Bulk Access Revocation [#bulk-access-revocation] **For Multiple Documents:** 1. **Select Documents**: Choose documents to revoke access 2. **Use Revoke Action**: Click "Revoke Access from Selected" 3. **Confirm Bulk Change**: Review the impact before proceeding 4. **Monitor Account Impact**: Check if account still has necessary access Access Revocation *Interface for revoking document access with confirmation* ### Emergency Access Removal [#emergency-access-removal] **Immediate Revocation Scenarios:** * Security breach or concern * Account relationship termination * Compliance requirement changes * Document sensitivity updates **Emergency Process:** 1. **Access Account Documents**: Navigate directly to account 2. **Select All Sensitive Documents**: Use bulk selection 3. **Immediate Revocation**: Remove access without delay 4. **Document Decision**: Record reason for emergency action 5. **Notify Stakeholders**: Inform relevant parties of the change ## Document Access Monitoring [#document-access-monitoring] ### Usage Tracking [#usage-tracking] **Monitored Metrics:** * **View Count**: Number of times document accessed * **Download Count**: Downloads by account users * **Last Accessed**: Most recent access timestamp * **Access Duration**: Time spent viewing documents * **User Activity**: Which users accessed which documents Access Monitoring *Document access analytics and usage tracking* ### Compliance Reporting [#compliance-reporting] **Audit Trail Features:** * **Permission Changes**: Complete history of access modifications * **User Attribution**: Who made each permission change * **Timestamp Accuracy**: Precise timing for compliance * **Reason Tracking**: Documentation of permission decisions **Report Generation:** * **Access Summary**: Current permissions across all accounts * **Change History**: Timeline of permission modifications * **Usage Analytics**: Document access patterns and trends * **Compliance Status**: Adherence to access policies ### Alert Configuration [#alert-configuration] **Notification Types:** * **Unusual Access Patterns**: Suspicious document access * **Access Violations**: Attempts to access restricted documents * **Permission Changes**: Notifications of access modifications * **Expiry Warnings**: Alerts for time-limited access approaching expiry ## Advanced Permission Features [#advanced-permission-features] ### Conditional Access [#conditional-access] **Requirements-Based Access:** * **Certification Status**: Access based on account certifications * **Review Completion**: Documents available after review complete * **Agreement Signing**: Access contingent on signed agreements * **Geographic Restrictions**: Location-based access controls ### Custom Access Workflows [#custom-access-workflows] **Approval Processes:** * **Manager Approval**: Require approval for sensitive documents * **Multi-Step Verification**: Multiple approvals for high-risk access * **Automated Workflows**: Rule-based permission assignment * **Escalation Procedures**: Process for handling access requests Advanced Permissions *Advanced permission features and workflow configuration* ### Integration Capabilities [#integration-capabilities] **API-Driven Access:** * **Programmatic Permission Management**: Automated access control * **External System Integration**: Sync with other platforms * **Real-Time Updates**: Immediate permission synchronization * **Bulk Operations**: Large-scale permission management ## Best Practices [#best-practices] ### Security-First Approach [#security-first-approach] **Principle of Least Privilege:** * Grant minimum necessary access * Regular access reviews and audits * Remove unused permissions promptly * Document access decisions **Access Review Schedule:** * **Monthly**: Review high-risk document access * **Quarterly**: Complete permission audit * **Annually**: Comprehensive access policy review * **Event-Driven**: Review after security incidents ### Operational Efficiency [#operational-efficiency] **Standardized Processes:** * Create access templates for common account types * Use bulk operations for similar accounts * Automate routine permission assignments * Document standard access patterns **Communication Standards:** * Notify accounts of significant access changes * Provide clear access instructions * Document access policies and procedures * Maintain help documentation for account users ### Compliance Management [#compliance-management] **Regulatory Adherence:** * Understand industry-specific access requirements * Implement appropriate controls and monitoring * Maintain detailed audit trails * Regular compliance assessments **Documentation Requirements:** * Keep records of all permission changes * Document business justification for access * Maintain evidence of access policy compliance * Prepare for regulatory audits ## Common Issues & Solutions [#common-issues--solutions] **Solution**: Check if the account's review status is "Completed" as some documents may be restricted to reviewed accounts only. Verify the document access level and ensure permissions were saved properly. **Solution**: Confirm you clicked "Save" after making changes. Check if there are any caching delays by asking the account to refresh their Trust Center page. Verify your role has permission to modify document access. **Solution**: Use the search and filter options to locate specific documents. Check if documents are marked as "Internal" and require special permissions. Verify the documents have been properly uploaded and categorized. **Solution**: Review access permissions from both original accounts, consolidate necessary access, remove duplicate permissions, and ensure the merged account has appropriate access without over-privileging. ## Multilingual Support [#multilingual-support] ### German - Dokumentenzugriff verwalten [#german---dokumentenzugriff-verwalten] **Zugriffsstufen:** * **Öffentlich**: Automatisch für alle Konten zugänglich * **Geschützt**: Explizite Berechtigung erforderlich * **Intern**: Hochgradig eingeschränkter Zugriff **Hauptaktionen:** * Dokumentzugriff gewähren und entziehen * Massenberechtigungen verwalten * Zugriff überwachen und analysieren ### French - Gérer l'accès aux documents [#french---gérer-laccès-aux-documents] **Niveaux d'accès:** * **Public**: Automatiquement accessible à tous les comptes * **Protégé**: Permission explicite requise * **Interne**: Accès hautement restreint **Actions principales:** * Accorder et révoquer l'accès aux documents * Gérer les permissions en masse * Surveiller et analyser l'accès ## Next Steps [#next-steps] Learn about managing documents and categories Configure advanced account settings and preferences Monitor document access and usage analytics ## Related Resources [#related-resources] * [Document Upload Guide](/docs/user-guide/documents/upload-documents) * [User Role Management](/docs/user-guide/users) * [API Reference - Document Access](/docs/api/v1/accounts/id/documents/get) *** Effective document access management ensures your customers have the right information while maintaining security and compliance. Use this guide to create a secure, efficient, and user-friendly document access experience. --- # Create New Account Source: https://docs.orbiqhq.com/docs/user-guide/accounts/create-account Step-by-step guide to creating and configuring new customer accounts in the Trust Center system # Create New Account [#create-new-account] Creating a new customer account is the first step in onboarding organizations to your Trust Center. This guide walks you through the complete account creation process, from basic information to advanced configuration options. ## What You'll Learn [#what-youll-learn] * How to access the account creation form * Required and optional account information * Contact management setup * Initial document access configuration * Account review process setup ## Prerequisites [#prerequisites] * **Admin** or **Account Manager** role required * Customer organization details ready * Contact information for key stakeholders ## Getting Started [#getting-started] ### 1. Navigate to Account Creation [#1-navigate-to-account-creation] From the main accounts page, click the **"Add Account"** button in the top-right corner. Add Account Button *Location of the Add Account button on the accounts overview page* ### 2. Account Creation Form [#2-account-creation-form] The account creation form is organized into several sections for efficient data entry. Account Creation Form *The complete account creation form with all required fields* ## Form Sections [#form-sections] ### Basic Information [#basic-information] **Account Name** (Required) * Enter the official organization name * This appears in the Trust Center and communications * Use the customer's preferred business name **Description** (Optional) * Brief description of the account or business relationship * Helpful for internal reference and organization * Example: "Primary logistics partner" or "Enterprise customer - GDPR compliance" 💡 **Naming Tip**: Use clear, recognizable names that your team will easily understand. Avoid internal codes or abbreviations. ### Contact Information [#contact-information] Add primary contacts for the account. You can add multiple contacts with different roles. **Contact Fields:** * **Email Address** (Required): Primary contact email * **First Name** (Required): Contact's first name * **Last Name** (Optional): Contact's last name * **Role** (Optional): Their role in the organization Contact Management *Contact information form with multiple contact support* **Adding Multiple Contacts:** 1. Fill in the first contact's information 2. Click **"Add Another Contact"** to include additional stakeholders 3. Specify roles to clarify responsibilities (e.g., "Compliance Officer", "IT Manager") ### Access Configuration [#access-configuration] **Access Level Settings:** **Review Status** * **Not Started** (Default): Account created but not yet reviewed * **In Progress**: Currently under compliance review * **Completed**: Fully reviewed and operational **Expiry Date** (Optional) * Set an optional expiration date for the account * Useful for temporary access or compliance cycles * Leave blank for permanent access ⚠️ **Expiry Notice**: Accounts with expiry dates will lose access to protected documents after expiration. Plan renewal processes accordingly. Access Configuration *Access level and expiry configuration options* ## Advanced Options [#advanced-options] ### Document Access Setup [#document-access-setup] During creation, you can pre-configure which document categories this account should access: * **Public Documents**: Always accessible to all accounts * **Protected Documents**: Require explicit permission * **Internal Documents**: Restricted to specific accounts only ### Notification Settings [#notification-settings] Configure how the account contacts should be notified: * **Welcome Email**: Automatic welcome message with access details * **Document Updates**: Notifications when relevant documents change * **Expiry Warnings**: Alerts before account expiration ## Creating the Account [#creating-the-account] ### 1. Form Validation [#1-form-validation] Before submission, ensure all required fields are completed: * ✅ Account name is provided * ✅ At least one contact email is valid * ✅ All contact information is accurate Form Validation *Form validation indicators showing required field completion* ### 2. Submit Account [#2-submit-account] Click **"Create Account"** to submit the form. The system will: 1. Validate all information 2. Create the account record 3. Set up initial permissions 4. Send welcome emails (if configured) 5. Redirect to the account details page ✅ **Success**: Once created, you'll be redirected to the new account's detail page where you can configure additional settings. ## Post-Creation Steps [#post-creation-steps] ### Immediate Actions [#immediate-actions] After creating an account, consider these immediate next steps: 1. **Configure Document Access**: Set specific document permissions 2. **Review Contact Details**: Verify all contact information is accurate 3. **Set Up Notifications**: Configure appropriate alert settings 4. **Initial Communication**: Reach out to introduce the Trust Center Account Details Page *The account details page immediately after creation* ### Document Assignment [#document-assignment] Navigate to the **Documents** tab to configure which documents this account can access: Configure document permissions for the new account ## Best Practices [#best-practices] ### Information Quality [#information-quality] * **Accurate Contacts**: Ensure email addresses are current and monitored * **Clear Descriptions**: Use descriptions that will be meaningful months later * **Appropriate Access**: Set expiry dates that align with business cycles ### Organization Standards [#organization-standards] * **Naming Conventions**: Use consistent naming patterns across accounts * **Contact Roles**: Clearly define each contact's responsibility * **Documentation**: Keep internal notes about special requirements ### Security Considerations [#security-considerations] * **Email Verification**: Confirm contact emails before granting access * **Access Levels**: Start with minimal access and expand as needed * **Review Cycles**: Set appropriate expiry dates for regular reviews ## Common Issues & Solutions [#common-issues--solutions] **Problem**: Contact email addresses showing as invalid **Solution**: Verify email format ([user@domain.com](mailto:user@domain.com)), check for extra spaces or special characters, confirm the email domain is valid and active, or try using a different email address temporarily. **Problem**: System rejects account name as duplicate **Solution**: Add a descriptor to make it unique (e.g., "Company Name - East Region"), include the customer's legal entity suffix, use the customer's preferred business name variation, or contact admin to verify if duplicate is intentional. **Problem**: Add contact button not working **Solution**: Ensure the current contact's required fields are filled, save current contact before adding another, refresh the page and try again, or use separate creation sessions for complex contact lists. ## Multilingual Support [#multilingual-support] ### German - Konto erstellen [#german---konto-erstellen] Hauptschritte: 1. **Kontoname**: Offizieller Organisationsname eingeben 2. **Kontakte**: Mindestens eine gültige E-Mail-Adresse hinzufügen 3. **Zugriff**: Ablaufdatum und Berechtigungen konfigurieren 4. **Erstellen**: Formular absenden und Details überprüfen ### French - Créer un compte [#french---créer-un-compte] Étapes principales: 1. **Nom du compte**: Saisir le nom officiel de l'organisation 2. **Contacts**: Ajouter au moins une adresse e-mail valide 3. **Accès**: Configurer la date d'expiration et les permissions 4. **Créer**: Soumettre le formulaire et vérifier les détails ## Next Steps [#next-steps] Learn how to edit and configure account settings Set up document permissions for the new account Invite team members to manage accounts ## Related Resources [#related-resources] * [Account Management Overview](/docs/user-guide/accounts) * [Document Management](/docs/user-guide/documents) * [API Reference - Create Account](/docs/api/v1/accounts/post) *** Ready to create your first account? Navigate to the accounts page and click **"Add Account"** to get started! --- # Account Management Source: https://docs.orbiqhq.com/docs/user-guide/accounts Manage customer organizations and their compliance journey through the Trust Center accounts system # Account Management [#account-management] The Account Management system is the heart of your Trust Center operations. Here you can create, configure, and manage customer organizations, track their compliance status, and control access to your trust center resources. ## What You'll Learn [#what-youll-learn] * How to view and filter customer accounts * Understanding account status indicators * Managing account details and settings * Configuring document access per account * Tracking compliance progress ## Prerequisites [#prerequisites] * **Admin** or **Account Manager** role required * Access to the Trust Center Admin interface ## Account Overview Dashboard [#account-overview-dashboard] The main accounts page provides a comprehensive view of all your customer accounts with powerful filtering and status tracking capabilities. ### Key Metrics Cards [#key-metrics-cards] The dashboard displays three important metric cards at the top: **🟢 Active Accounts** * Shows completed accounts that are fully onboarded * Click to filter and view only active accounts * These accounts have completed their compliance review **🟡 Not Started** * Displays accounts that haven't begun the compliance process * Default filter when you have pending accounts * Requires immediate attention for onboarding **🔴 Expiring Soon** * Shows accounts with access expiring within 30 days * Critical for maintaining continuous compliance * Helps prevent service interruptions Account Overview Dashboard *The main accounts dashboard showing metric cards and account listings* ### Account Listing Table [#account-listing-table] The accounts table provides detailed information for each customer: | Column | Description | | ----------------- | ---------------------------------------------------- | | **Name** | Customer organization name and identifier | | **Description** | Brief description of the account purpose | | **Expiry** | Access expiration date with visual status indicators | | **Review Status** | Current compliance review state | #### Review Status Indicators [#review-status-indicators] **Status Colors:** - 🟢 **Completed**: Account fully reviewed and active - 🟡 **Not Started**: Account created but review pending - 🔵 **In Progress**: Currently under review - ⚪ **Cancelled**: Review process cancelled ### Search and Filtering [#search-and-filtering] Use the search bar to quickly find specific accounts by: * Account name * Description content * Contact information **Filter Options:** * **Active Accounts**: Shows only completed, operational accounts * **Not Started**: Displays accounts awaiting initial review * **Expiring Soon**: Shows accounts nearing expiration (\< 30 days) {/* ![Account Search and Filter](/screenshots/accounts/search-filter.png) */} {/* _Search functionality and filter options for account management_ */} ## Account Actions [#account-actions] ### Creating New Accounts [#creating-new-accounts] Click the **"Add Account"** button to create a new customer account. This launches the account creation workflow with guided steps. Step-by-step guide to creating customer accounts ### Managing Existing Accounts [#managing-existing-accounts] Click on any account row to access detailed management options: * **Account Details**: Edit basic information and contacts * **Documents**: Manage document access and permissions * **Settings**: Configure access expiry and review settings * **Activity**: View account activity log and changes Configure account information and settings Control document access per account ## Account Status Management [#account-status-management] ### Expiry Date Management [#expiry-date-management] Accounts can have optional expiry dates that control access to the Trust Center: * **Green Status**: Account active with >30 days remaining * **Amber Status**: Account expiring within 30 days * **Red Status**: Account expired or past expiry date ⚠️ **Important**: Expired accounts lose access to protected documents and require renewal to restore functionality. ### Review Process States [#review-process-states] The review status tracks the compliance onboarding process: 1. **Not Started**: Account created, awaiting initial review 2. **In Progress**: Currently undergoing compliance assessment 3. **Completed**: Fully reviewed and operational 4. **Cancelled**: Review process halted {/* ![Account Status Management](/screenshots/accounts/status-management.png) */} {/* _Visual representation of account status indicators and their meanings_ */} ## Best Practices [#best-practices] ### Account Organization [#account-organization] * Use clear, descriptive account names * Include relevant business context in descriptions * Set appropriate expiry dates for compliance cycles * Regularly review and update account statuses ### Access Management [#access-management] * Grant document access based on compliance requirements * Monitor expiring accounts proactively * Maintain accurate contact information * Document any special access arrangements ### Workflow Efficiency [#workflow-efficiency] * Use filters to focus on accounts requiring attention * Process "Not Started" accounts promptly * Set up monitoring for expiring accounts * Leverage search for quick account location ## Common Tasks [#common-tasks] Currently, expiry dates must be updated individually through the account details page. Navigate to the specific account and update the expiry date in the settings tab. Account visibility is controlled by your role permissions. **Viewers** can only see accounts, while **Account Managers** and **Admins** can see and modify all accounts. Review status changes are typically handled automatically through the compliance workflow. Manual status changes can be made by **Admins** in the account settings. ## Next Steps [#next-steps] Learn how to set up new customer accounts Configure which documents accounts can access Manage team members and permissions ## Troubleshooting [#troubleshooting] ### Performance Issues [#performance-issues] * Use filters to reduce large account lists * Search by specific terms rather than browsing * Contact support if loading times exceed 10 seconds ### Access Problems [#access-problems] * Verify your role has account management permissions * Check if accounts are filtered by status * Confirm you're logged into the correct tenant *** Need help with account management? Check our [support documentation](/docs/user-guide/login) or contact the admin team. --- # Manage Account Details Source: https://docs.orbiqhq.com/docs/user-guide/accounts/manage-account Update account details, contacts, document access, internal notes, and activity history # Manage Account Details [#manage-account-details] The account detail page is where you maintain the customer record behind document access and Trust Center activity. ## Access [#access] * **Admin** * **Account Manager** * **Content Manager** ## Account Tabs [#account-tabs] The account screen is organized around three tabs: * **Documents** * **Contacts** * **Settings** An activity feed is shown alongside the main editing area. ## Settings Tab [#settings-tab] The Settings tab covers the fields that are actually editable here: * Account name * Description * Internal notes * Custom fields ## Contacts Tab [#contacts-tab] Use the Contacts tab to review and update the stakeholders attached to the account. ## Documents Tab [#documents-tab] Use the Documents tab to control which documents this account can access. This is where you grant or remove document sharing for the account. ## Related Docs [#related-docs] * [Account documents](/docs/user-guide/accounts/account-documents) * [Access requests](/docs/user-guide/access-requests) * [Contacts](/docs/user-guide/contacts) --- # Analytics & Insights Source: https://docs.orbiqhq.com/docs/user-guide/analytics Review Trust Center usage trends, top documents, contact activity, account activity, and search volume # Analytics & Insights [#analytics--insights] The Analytics page summarizes how people use your Trust Center. ## Access [#access] * **Admin** * **Account Manager** * **Content Manager** * **Viewer** ## Summary Cards [#summary-cards] The top row shows four trend cards for the selected period: * Total document views * Total downloads * Active contacts * Total searches Each card compares the current period with the previous period. ## Time Ranges [#time-ranges] The UI includes quick filters for: * Last 7 days * Last 30 days * Last 90 days * Month to date * Last month * Year to date * Last year ## Detailed Sections [#detailed-sections] Below the summary cards, the page breaks analytics into four practical views: * **Document analytics**: views and downloads per document * **Contact activity**: which contacts accessed documents and when * **Account activity**: usage grouped by account * **Search analytics**: popular search queries and total search count ## Related Docs [#related-docs] * [Accounts](/docs/user-guide/accounts) * [Account documents](/docs/user-guide/accounts/account-documents) * [Access requests](/docs/user-guide/access-requests) --- # Full Custom CSS Source: https://docs.orbiqhq.com/docs/user-guide/brand/full-custom-css Apply advanced CSS to the Trust Center # Full Custom CSS [#full-custom-css] The Brand → Advanced section lets you inject custom CSS into the Trust Center head. Use it for edge cases only; malformed rules can break layouts. Scripts and `@import` are stripped.
Use minimal, scoped overrides. Avoid global resets. Keep a copy of your CSS so you can quickly revert.
## How to enable [#how-to-enable] 1. In Admin Center, go to **Brand → Advanced** (Brand-Extended CSS accordion). 2. Paste your CSS into the editor and **Save changes**. 3. Verify in the Trust Center; the CSS is injected before `` and re-sanitized on save. ## Available selectors [#available-selectors] * **Global**: `.trust-center-body`, `.trust-center-shell[data-tc-surface]` * **Markdown**: `[data-tc-markdown]` wrapper, `.markdown-viewer` (overview, hero, resource previews) * **Tabs shell**: `[data-tc-tabs-root]`, `[data-tc-tabs]`, `[data-tc-tabs-header]`, `[data-tc-tabs-list]`, `[data-tc-tab-trigger]`, `[data-tc-tabs-body]` * **Overview tab**: `[data-tc-tab-panel="overview"]`, `[data-tc-overview-grid]`, `[data-tc-overview-left]`, `[data-tc-overview-right]`, `[data-tc-overview-resources]`, `[data-tc-overview-resources-item]`, `[data-tc-overview-resources-item-title]`, `[data-tc-overview-categories]`, `[data-tc-overview-category]`, `[data-tc-overview-category-doc]`, `[data-tc-overview-category-doc-title]`, `[data-tc-overview-subprocessors]`, `[data-tc-overview-faq]` * **Other tabs**: `[data-state=active]` on tab triggers; wrap styles with `[data-tc-tab-panel="documentation"]`, `[data-tc-tab-panel="subprocessors"]`, `[data-tc-tab-panel="faq"]` * **FAQ (full tab)**: `[data-tc-faq]`, `[data-tc-faq-header]`, `[data-tc-faq-list]`, `[data-tc-faq-accordion]`, `[data-tc-faq-item]`, `[data-tc-faq-question]`, `[data-tc-faq-answer]` * **Modals**: `[data-tc-modal]` (generic), `[data-tc-modal="base"]`, `[data-tc-modal="alert"]`, `[data-tc-modal="document"]`, `[data-tc-modal="request-access"]`, `[data-tc-modal="nda"]` * **Header search**: `[data-tc-search]`, `[data-tc-search-input]`, `[data-tc-search-results]`, `[data-tc-search-result]`, `[data-tc-search-section="knowledge"]`, `[data-tc-search-section="documents"]`, `[data-tc-search-section="subprocessors"]`, `[data-tc-search-empty]` * **AI answers**: `[data-tc-search-answer-loading]`, `[data-tc-search-ai-answer]`, `[data-tc-search-answer-panel]`, `[data-tc-search-answer="complete"]`, `[data-tc-search-answer="error"]` * **Agent toolkit**: `[data-tc-agent-toolkit-trigger]`, `[data-tc-agent-toolkit]`, `[data-tc-agent-toolkit-action]`, `[data-tc-agent-toolkit-copy]` * **Avatar**: `[data-tc-avatar]`, `[data-tc-avatar-image]`, `[data-tc-avatar-fallback]` * **UI atoms**: `.card`, `.badge`, `.button` variants follow CSS variables; prefer tokens over hard-coded values ## CSS tokens you can rely on [#css-tokens-you-can-rely-on] These map to tenant brand settings and system theming: * `--primary`, `--primary-hover` * `--background`, `--foreground` * `--card`, `--card-foreground` * `--muted`, `--muted-foreground` * `--border`, `--input` * `--markdown-font-family` Use them for subtle tweaks instead of hard-coded colors when possible. ## Full example [#full-example] ```css /* Soften page background and cards */ .trust-center-shell[data-tc-surface] { background: radial-gradient(circle at 20% 20%, #eef3ff, #ffffff 40%); } [data-tc-tabs-root] { border: 1px solid hsl(var(--border)); border-radius: 10px; background: hsl(var(--card)); } [data-tc-tab-trigger][data-state="active"] { border: 1px solid hsl(var(--primary)); background: hsl(var(--primary) / 0.08); color: hsl(var(--primary)); } .trust-center-shell .card { border-radius: 18px; box-shadow: 0 16px 40px -24px rgba(0, 0, 0, 0.25); } /* Typography tweaks for markdown */ .markdown-viewer h2 { font-size: 1.35rem; letter-spacing: -0.01em; color: hsl(var(--primary)); } .markdown-viewer a { text-decoration: underline; text-decoration-thickness: 2px; text-underline-offset: 4px; } /* Badge styling */ .badge, .badge-outline { border-radius: 12px; text-transform: uppercase; letter-spacing: 0.05em; } /* Overview panels */ [data-tc-tab-panel="overview"] [data-tc-overview-category], [data-tc-overview-resources], [data-tc-overview-compliance], [data-tc-overview-subprocessors], [data-tc-overview-faq] { border: 1px solid hsl(var(--border)); border-radius: 18px; box-shadow: 0 14px 36px -24px rgba(0, 0, 0, 0.22); background: hsl(var(--card)); } [data-tc-overview-resources-item], [data-tc-overview-category-doc] { border-radius: 12px; transition: transform 160ms ease, box-shadow 160ms ease; } [data-tc-overview-resources-item]:hover, [data-tc-overview-category-doc]:hover { transform: translateY(-2px); box-shadow: 0 10px 24px -20px rgba(0, 0, 0, 0.3); } [data-tc-overview-resources-item-title], [data-tc-overview-category-doc-title] { font-weight: 700; } /* FAQ (overview preview) */ [data-tc-overview-faq-item] { border: 1px solid hsl(var(--border)); border-radius: 12px; padding: 10px 12px; } [data-tc-overview-faq-question] { font-weight: 700; } [data-tc-overview-faq-answer] { color: hsl(var(--muted-foreground)); } /* FAQ tab */ [data-tc-faq-item] { border: 1px solid hsl(var(--border)); border-radius: 12px; background: hsl(var(--card)); } [data-tc-faq-question] { font-weight: 700; } [data-tc-faq-answer] { color: hsl(var(--muted-foreground)); } /* Preserve default spacing on mobile */ @media (max-width: 640px) { .trust-center-shell .card { padding: 14px; } } ``` ## Targeted examples [#targeted-examples] Change overview card borders and shadow: ```css [data-tc-tab-panel="overview"] [data-tc-overview-category], [data-tc-overview-resources], [data-tc-overview-compliance] { border: 1px dashed hsl(var(--primary)); border-radius: 18px; box-shadow: 0 12px 30px -18px rgba(0, 0, 0, 0.25); } ``` Style FAQ preview cards (overview): ```css [data-tc-overview-faq-item] { border: 1px solid hsl(var(--border)); border-radius: 12px; padding: 10px 12px; } [data-tc-overview-faq-question] { font-weight: 700; } [data-tc-overview-faq-answer] { color: hsl(var(--muted-foreground)); } ``` Hide the agent toolkit: ```css [data-tc-agent-toolkit-trigger], [data-tc-agent-toolkit] { display: none !important; } ``` Style the header search input and results: ```css [data-tc-search-input] { border-radius: 999px; border-color: hsl(var(--primary)); } [data-tc-search-results] { border: 1px solid hsl(var(--border)); box-shadow: 0 24px 40px -32px rgb(0 0 0 / 0.35); } [data-tc-search-result]:hover { background: hsl(var(--primary) / 0.06); } ``` Emphasize AI answers: ```css [data-tc-search-answer="complete"] { border-color: hsl(var(--primary)); background: linear-gradient( 135deg, hsl(var(--background)), hsl(var(--primary) / 0.08) ); } ``` Style the account avatar: ```css [data-tc-avatar] { box-shadow: 0 0 0 2px hsl(var(--background)), 0 0 0 4px hsl(var(--primary)); } [data-tc-avatar-fallback] { font-weight: 700; color: hsl(var(--primary)); } ``` Customize full FAQ tab accordion (scope-safe): ````css [data-tc-tab-panel="faq"] .accordion-item { border: 1px solid hsl(var(--border)); border-radius: 12px; margin-bottom: 10px; } [data-tc-tab-panel="faq"] .accordion-trigger { font-weight: 600; padding: 12px 14px; } [data-tc-tab-panel="faq"] .accordion-content { padding: 0 14px 12px; color: hsl(var(--muted-foreground)); } Experiment with tabs squared and flat: ```css [data-tc-tabs-root] { border: 1px solid hsl(var(--border)); border-radius: 8px; background: hsl(var(--card)); } [data-tc-tab-trigger] { border-radius: 6px; padding: 8px 12px; border: 1px solid transparent; } [data-tc-tab-trigger][data-state="active"] { border-color: hsl(var(--primary)); background: hsl(var(--primary) / 0.08); color: hsl(var(--primary)); } ```` FAQ neon (alternative): ```css [data-tc-faq-item] { position: relative; border: 0; border-radius: 18px; background: linear-gradient(135deg, #0f172a 0%, #111827 60%, #1e293b 100%); color: #e2e8f0; box-shadow: 0 16px 40px -24px rgba(0, 0, 0, 0.6), 0 0 0 1px rgba(255, 255, 255, 0.04); padding: 6px 10px; overflow: hidden; } [data-tc-faq-item]::before { content: ""; position: absolute; inset: 0; border-radius: 18px; background: radial-gradient( circle at 20% 20%, rgba(59, 130, 246, 0.22), transparent 50% ); pointer-events: none; } [data-tc-faq-question] { padding: 14px 16px; font-weight: 700; letter-spacing: -0.01em; color: #e2e8f0; } [data-tc-faq-answer] { padding: 0 16px 16px 16px; color: #cbd5e1; } ``` Tables squared with header background: ```css .markdown-viewer table { width: 100%; border-collapse: collapse; border: 1px solid hsl(var(--border)); } .markdown-viewer th, .markdown-viewer td { border: 1px solid hsl(var(--border)); padding: 8px 10px; } .markdown-viewer thead { background: hsl(var(--primary) / 0.1); color: hsl(var(--primary)); } ``` ### Modal styling examples [#modal-styling-examples] Base modal theme: ```css [data-tc-modal] { border-radius: 16px; box-shadow: 0 24px 64px -32px rgba(0, 0, 0, 0.4); background: hsl(var(--card)); } ``` Per-modal overrides: ```css [data-tc-modal="document"] { border: 1px solid hsl(var(--primary)); } [data-tc-modal="request-access"] { border: 1px solid hsl(var(--border)); background: hsl(var(--card)); } [data-tc-modal="nda"] { background: linear-gradient(135deg, #0f172a, #1f2937); color: #e2e8f0; } [data-tc-modal="alert"] { border: 1px solid hsl(var(--destructive)); } ``` Modal buttons: ```css [data-tc-modal] .button, [data-tc-modal] button { border-radius: 10px; font-weight: 600; } ``` ## Safety limits and sanitization [#safety-limits-and-sanitization] * Max length: \~50 KB of CSS. * Stripped: `