Settings

​

Navigating through Account Settings

• My Profile — your personal account and notification preferences.
• Workspace — General, Members, Roles, and Groups.
• Features — Integrations and Data Models.
• Security — API Keys.

​

My Profile

• Profile picture: Under Avatar, click your picture to change it.
• User Details: Set the First Name and Last Name that appear across the platform.
• Appearance: Choose how the app looks to you — Light, Dark, or System.
• Email Notifications: Configure how you receive email alerts. For example, toggle Task Notifications to be alerted about upcoming and overdue tasks. Task alerts are sent daily for incomplete tasks past due or due within the next 2 days.

​

Workspace

​

General

• Company Website: Add your company URl to tailor AI recommendations across discovery, chat, and more.
• Data & Privacy: Manage workspace exports, file uploads, and integrations.
• CRM Settings: Configure notes, associated contacts, organizations, and meetings.
• Tasks: Manage tasks directly tied to contracts or organizations.
• AI Actions: Allows Ai to create pipeline records, tasks, notes, ect.
• Workspace Data Search: Allows Chat to search your workspace data.

Note: Pryzm does not use your data to train our AI across any of our modules.

​

Adding members

​

Removing or replacing a user

​

Roles

• Admin: Can manage everything in the workspace.
• Editor: Can manage most things, with restrictions on higher-security features.
• Viewer: Read-only access to everything in the workspace.

​

How rules work (and the per-role breakdown)

​

Groups

1. On the Groups page, select Create Group.
2. Enter a Name (for example, Finance).
3. Optionally add a Description of what the group is responsible for.
4. Select Create Group.

​

Features

​

Integrations

• Connected Account: Shows the authorized account, with a Manage option.
• Integration Status: Each service (such as Gmail and Google Calendar) shows as Active with a Disconnect option, so you can control each one independently.
• What you get and Privacy & Security explain the scope of access. Pryzm uses OAuth 2.0 and only accesses the data you authorize.

Note: Once connected, emails, calendar events, Slack, and contacts sync automatically. Contacts appear under Records → People, and related organizations are created under Records → Organizations based on email domains.

​

Connect your email and calendar in Pryzm

1. Go to the Integrations page. Under the Personal Integrations section (“Connect your personal accounts to enhance your workflow”), you’ll see the email/calendar options.
2. Pick your provider:
   • Gmail + Calendar — connect your Google account to search email threads and sync calendar events.
   • Outlook + Calendar — connect your Microsoft account for the same.
3. Click the card for your provider. Hovering shows a → arrow indicating it’s clickable; clicking it kicks off the connection.
4. Sign in with your provider. For Gmail, a “Sign in with Google → Choose an account to continue to Pryzm” screen appears. Select the account you want to connect (or Use another account to sign in with a different one). The Outlook path opens the equivalent Microsoft sign-in.
5. Grant the requested permissions so Pryzm can read your email threads and sync calendar events.
6. You’re returned to the Integrations page, and the card will show a green ✓ Connected badge — the same way the Email Relay card shows as connected in your workspace.

• These are personal integrations, so each user connects their own account; this is separate from the Workspace Integrations (Slack, Salesforce) lower on the page.

​

Integration Settings

• Record Creation — control how contacts are automatically created from emails and calendar events:
  • No Creation: No records are created automatically; events still associate with records you create manually.
  • Selective (Recommended): Records are created only for contacts who email your workspace members or appear in their calendar events.
  • All Contacts: Records are created for every contact in synced emails and calendar events.
• Sharing Visibility — control what email data team members can see on shared records:
  • No Sharing: Threads are visible only to the owner.
  • Metadata Only: Members see subject lines, participants, and dates, but not the message body.
  • Full Visibility: The full body, subject line, and attachments are shared.
• Email Filters: Use an Allowlist or Blocklist to control which domains and addresses are processed.
• Auto-Enrich Contacts: Enrich contact data with company info, job titles, and social profiles.
• Forwarded Email Discovery: When a member forwards an email, automatically extract and store the original sender and recipients as thread participants, making forwarded contacts searchable in contact records.
• Email & Calendar Integration Access: Choose Unrestricted (all members can connect) or Restricted (only approved members can connect) for email and calendar integrations.
• Team Integrations: Admins can see which members have connected and which integration they completed.

​

Salesforce

​

Email Relay

​

Slack

1. Go to Integrations under Workspace Features.
2. Select Slack from the available connectors.
3. Select Connect and authorize the Slack workspace where you want to receive alerts.

​

Data Models

​

Adding a New Object

1. On the Data Models page, select Create data model.
2. Pick a template to start from, or choose Create your own to build from scratch.
3. Open the new object to configure its Attributes, Appearance, Policies, Permissions, and other settings.

• Deals — a capture pipeline based on the Shipley method, from inbound identification through procurement and close.
• Customer Success — monitor customer health from onboarding through renewal.
• Fundraising — track investor outreach from research through term sheets.
• Commercial Sales — a classic B2B sales pipeline from lead generation to close.
• Press Outreach — manage pitches, follow-ups, and published coverage.

​

Configuring a Data Model

• Configuration — the model’s core settings.
• Attributes — its fields and data structure.
• Appearance — how the model is displayed.
• Apps — connected apps for the model.
• Policies — automation and data policies.
• Permissions — who can access the model’s records.
• Webhooks — outbound HTTPS callbacks for the model.

1. Go to the Attributes tab.
2. Select Create attribute.
3. Choose a field type.
4. Save.

1. On the Attributes tab, find the attribute you want to change.
2. Select the attribute to open its settings.
3. Edit what you need — its name, type-specific settings, and (for Select / Multi-select fields) add to the list of options and change icon appearance.
4. Save your changes.

1. Drag an attribute by its handle on the left hand side to move it up or down.
2. The order here controls how fields appear on the record card.

1. Open the attribute and add any rules or approval requirements that should apply when its value changes.
2. Save. (Approval requests then surface in the pipeline’s top banner and on the affected record card.)

1. Open the attribute (or use its row menu) and choose Delete.

• System fields are locked. Core attributes are marked System and can’t be edited or deleted.
• Changes apply across the model. Edits to an attribute reflect on every record of that data model, so renaming or changing options updates all existing records’ fields.

1. Open the object you want to add the link to and go to its Attributes tab.
2. Select Create attribute and choose the Relationship field type.
3. Choose the object whose records this field should link to (for example, People or Organizations).
4. Save the attribute. You can now associate records from that object on any record of this one.

1. On the Appearance tab, find the Record Page card and click Open designer to edit the layout people see when they open a record (it edits live, with placeholder values).
2. In the designer, edit any of these:
   • Click + Add a stage banner to put a stage progress bar across the top.
   • Click + Add widget to surface a specific field (e.g., Competition Level).
   • Click + Add a section to add a grouped app block (Tasks, Notes, Files, Deal Plan, etc.).
   • Click + Add tab to add a tab, choosing a built-in tab or one from a relationship (e.g., Organizations); drag tabs to reorder.
3. Back on the Appearance tab, under Card fields, click + Add field to choose what shows beneath the title; drag the handles to reorder, or click the trash icon to remove a field.
4. Under Card icon, click + Choose source to change the icon.
5. Under Creation panel, click + Change document to attach a doc shown beside the create form (or Reset to clear it).

1. On the Apps tab, use the toggle on the right of each app to control whether it appears on records — Tasks, Notes, Files, Meetings, Emails, Proposal, Products, and Orion.

1. Click the gear icon on an app to edit its sources — shown as Direct (items tied straight to the record) or, for example, 2 sources (items pulled through related records).
2. Meetings and Emails are matched by email address, so use their source settings to pull in meetings and threads from related contacts.

1. Scroll to Data links on the Apps tab.
2. Find the opportunity group you want to edit (Contracts, Grants, or Foreign opportunities).
3. Locate the Opportunity field row you want to change (e.g., Title, Posted date, Response deadline, Description, Points of contact, Government organization).
4. In that row, open the Pipeline attribute dropdown and pick the attribute it should fill — for example, Title → Name, Posted date → Start Date, Response deadline → Close Date.
5. To stop a field from pre-filling, set its dropdown to Not mapped.
6. Click Save.

• Relationship fields resolve to linked records, not text. Points of contact maps to your Contacts attribute and links the matching People records; Government organization maps to Organizations and links the issuing agency.
• Each opportunity type maps independently. A Grant’s Application deadline and a Contract’s Response deadline can both point to Close Date, but you set them in their own tables — changing one doesn’t change the other.
• Mappings apply only at creation. They pre-fill a record the moment it’s created from an opportunity; changing them later doesn’t rewrite existing records.Policies — edit automation rules and notifications

1. On the Policies tab, use the Rules / Notifications toggle (top right) to pick what you’re editing.
2. To add or edit a Rule, click + Create rule, then choose a type: Require approval, Require a reason, or Require prerequisites.
3. Configure the rule:
   • When this happens: pick the trigger — Choice or status, Field changes, Record created, or No activity — and select the attribute it applies to.
   • Require: set what’s needed (for approvals: Require approval from Any one / all, then + Add approver; for prerequisites: set the required fields and conditions).
   • Only when (optional): click Add condition for an extra check on the record’s current state.
4. Save the rule (e.g., Require approval), or click Cancel to discard.
5. To edit notifications, switch to Notifications and choose Slack (post to a channel) or Email (send to a recipient).

1. On the Permissions tab, set General access — the scope (e.g., Workspace) or a restricted setting.
2. Choose the Default access level everyone with access gets (e.g., Editor or Viewer).
3. Grant specific people their own access level, including Owner.

​

Webhooks

Note: Only admins can create or deactivate webhook subscriptions. Webhook subscriptions are tied to a specific pipeline and managed in the Pryzm frontend.

• webhook_type currently supports only campaign.created.v1.
• target_url must be a public HTTPS URL.
• Pryzm returns the signing secret only once, when the webhook is created — store it when you receive the response.

{
  "event": "campaign.created.v1",
  "event_timestamp": "2026-04-09T14:23:11.000000+00:00",
  "data": "<campaign record payload>"
}

1. Read the raw request body exactly as sent.
2. Build the signed payload as <timestamp>.<raw_body>.
3. Compute the HMAC SHA-256 digest using your webhook secret.
4. Compare the digest to v1 from X-Pryzm-Signature.

import hashlib
import hmac

timestamp = request.headers["X-Pryzm-Timestamp"]
signature = request.headers["X-Pryzm-Signature"]
raw_body = request.get_data(as_text=True)

signed_payload = f"{timestamp}.{raw_body}".encode()
expected = hmac.new(WEBHOOK_SECRET.encode(), signed_payload, hashlib.sha256).hexdigest()
received = signature.split("v1=", 1)[1]

is_valid = hmac.compare_digest(expected, received)

• Deliveries use a 5 second timeout, and redirects are not followed.
• Pryzm retries on network errors and on 429 and 5xx responses, but not on other 4xx responses.
• Retries use exponential backoff with jitter, starting at 120 seconds and capped at 1800 seconds, for up to 6 total attempts.
• If a webhook reaches 50 consecutive final-attempt failures, Pryzm deactivates it and emails the owner.

​

Security

​

API Keys

Note: Only admins can create API keys. Members without the required permissions will see an Access Denied message and should contact their workspace administrator.

​

SAML (SSO)

1. Open the SAML Configuration section (direct link).
2. Select Edit on the SAML configuration page.
   
3. Switch the Require SAML login toggle to ON.
   
4. Confirm and select Save Changes.

Warning: Once SAML enforcement is on, users can only log in with SAML. Fully test your configuration before enabling this to prevent workspace lockout.