Understand one-way SaaS API-token storage | Pixie CRM Help Centre Canonical: https://pixiecrm.com/help-centre/understand-one-way-saas-api-token-storage Publisher: Pixie Technologies LLC Core CRM security hardening Understand one-way SaaS API-token storage Pixie CRM guidance. Follow the route for your workspace, check your role and enabled modules, and verify the result before moving on. This guide explains why SaaS API tokens are stored as non-recoverable server-side representations. Audience: Administrators and deployment engineers; Permission: Core release / deployment authority; Where to goAutomatic core protection — no separate staff menu route What this guide helps you do Understand why SaaS API tokens are stored as non-recoverable server-side representations. The workflow below follows the supported application or module flow and does not invent a menu or bypass validation. Follow these steps - Use the supported Pixie CRM release or workflow that produces this security control. - Check the expected protection through an authorised test. - Record the result in the deployment or security audit evidence. Fields and options - Token purpose - Controlled token value - One-way stored representation Rules and limits - The usable token is shown only through its controlled creation or rotation workflow. - The server stores a one-way representation and validates presented tokens without recovering plaintext. - Store the client copy in an approved secret manager. Check it worked - The protection is active without weakening another security control. Security, audit and troubleshooting checks - Use the exact authorised account, role and record before saving or sending. - Verify the saved status and downstream record; a browser success message alone is not sufficient evidence. - Never expose passwords, API keys, access tokens, protected attachments or raw server paths in support tickets. - Do not edit module or core database records directly to bypass validation, permissions, migrations or state rules. Related guides Understand restricted CSRF exclusions (https://pixiecrm.com/help-centre/understand-restricted-csrf-exclusions)Manage API-token expiry, revocation, rotation and usage metadata (https://pixiecrm.com/help-centre/manage-api-token-expiry-revocation-rotation-and-usage-metadata)Verify the corrected two-factor assignment flow (https://pixiecrm.com/help-centre/verify-the-corrected-two-factor-assignment-flow)Configure trusted reverse-proxy handling safely (https://pixiecrm.com/help-centre/configure-trusted-reverse-proxy-handling-safely) Connected discovery, service and API guides Gateway one-way portal token storage (https://pixiecrm.com/help-centre/proplix-secure-api-gateway-portal-profiles-tokens-hash)Gateway one-way key hashes (https://pixiecrm.com/help-centre/proplix-secure-api-gateway-security-rate-ip-token-one-way)