Organization
The Organization page is where admins manage the workspace itself - its identity, the people in it, and pending invitations. It's the first place a new admin lands when setting up Sift, and the place to return to when adding teammates, changing roles, or updating the org's branding.
The Organization profile is divided into two tabs:
General - Edit the organization's name, slug, and logo / avatar. These appear throughout the app and on shared links.
Members - View the full list of members in the org along with their role. Admins can change a member's role or remove them. Each member row shows their name, email, role, and the date they joined.
Integrations
The Integrations page is the central hub for connecting Sift to the platforms it listens to and replies on. Every connected platform feeds Sift's pipelines - populating the Inbox, the Analytics dashboards, and the Users tab - and disconnecting one stops the corresponding data flowing in.
Connections are presented as a responsive grid of integration tiles. Each tile shows the platform's logo, its name, and a status indicator that flips to "Active" once the platform is connected. Clicking a tile opens that platform's dedicated connection flow, where you can authenticate accounts, choose what to monitor, and configure platform-specific options.
Supported platforms
Social
Facebook, Instagram (via the Facebook connection), X / Twitter, TikTok, YouTube, LinkedIn, Threads
Messaging
Discord, Telegram, WhatsApp
Reviews
App Store, Google Play (via Google)
Integration Health
The Integration Health page is the monitoring dashboard for the OAuth tokens behind your connected social accounts. When a token expires or gets revoked — for example because a Facebook page admin changed their password or revoked Sift's access — that account stops working silently. Token Health surfaces those failures so they can be fixed before they cause data gaps.
Accounts table
Below the banner is a table with one row per connected account. Each row shows:
Platform
The platform icon and name (Facebook, Instagram, X / Twitter, or Google).
Account
The connected account name, plus the associated email when different.
Status
A Valid or Invalid badge.
Last Checked
Timestamp of the most recent token check.
Notifications
The Notifications page connects your Slack workspace to Sift. Once Slack is connected, workflows can post notifications into the channels you choose - for example to alert a team about a viral post, a CSAT spike, or a new high-value detractor - without anyone needing to log into the Sift app.
A header card at the top of the page introduces the integration with a short description: connect your Slack workspace so workflow steps can route notifications into Slack channels. This is purely informational and explains what the connection enables.
The connection card itself contains the Connect Slack action. Clicking it runs the standard Slack OAuth flow - Slack will ask you to authorize Sift's access to the workspace and confirm which channels Sift can post into.
After authorization, the connection is complete and Slack channels become available as destinations inside any workflow that includes a notification step. Subsequent visits to this page show the existing connection and let you reauthorize or disconnect.
Org Preferences
The Org Preferences page is a single page that gathers every workspace-wide default that doesn't belong on its own dedicated screen — timezone, URL shortening, dashboard theming, AI-assisted reply behavior, and API keys.
Organization Timezone
A single timezone selector that determines how dates and times are displayed across org-level reporting and scheduling - for example daily roll-ups, charts, and any time-of-day grouping in Analytics.
Changes take effect immediately and are confirmed with a toast.
URL Shortening
Controls how outbound replies handle long URLs. Two settings:
Enable URL shortening - A toggle that turns shortening on or off for the workspace.
Minimum URL length - A numeric input (20–200) that sets the threshold above which a URL gets shortened. Shorter URLs are left as-is. The field is disabled while the toggle is off.
A Save button at the bottom of the card persists changes once you've made any edits.
Default Dashboard Theme
A row of color-theme presets that apply to new dashboards created in the workspace. Each preset is a small swatch showing the colors that will be used for charts, with the active preset highlighted. Users can still override the theme on a per-dashboard basis from inside the dashboard builder.
AI-Assisted Replies
The most substantive card on the page. Two controls govern how Sift learns from your team's reply history.
Enable AI-assisted replies is a toggle that opts the org into the feature. When enabled:
Sift reviews recent replies across all platforms to identify effective response patterns.
Patterns are grouped by scenario (billing questions, escalations, feature requests, and so on).
The AI assistant uses these patterns to draft replies that match your team's voice.
Patterns are continuously refined as your team sends more replies.
On first enable, Sift analyzes the last 30 days of replies; after that, new replies are processed daily.
Reply guidance is a large textarea where admins write the freeform instructions the AI should follow when drafting replies - tone, escalation policy, what not to ask for in public channels, when to move customers to DM, and so on. A sensible default is pre-populated and is fully editable.
A Save button at the bottom of the textarea persists guidance changes.
API Keys
The final card embeds the API key management interface. Admins can:
Create a new API key with a name and scopes.
List existing keys with their name, prefix, scopes, and last-used timestamp.
Revoke a key when it's no longer needed.
API keys grant programmatic access to the workspace via the Sift API, so they should be treated as sensitive credentials.
Invite Users
The Invite Users page is a dedicated bulk invitation flow for adding many teammates to the workspace at once. It is gated behind the sift_invite_users feature flag and is only visible to Super Admins. Single, ad-hoc invitations can still be sent through Organization → Members, but this page is the better choice when onboarding a whole team.
How it works
The page contains a single card. Three controls drive an invitation batch:
Email Addresses - A multi-email input. Press Enter or comma to add an email; you can also paste a list of addresses and they'll be split apart automatically. Each added email becomes a removable chip below the input. A helper line below the field reminds you of the supported input methods.
Role - A dropdown to pick the default role for everyone in the batch. Two options are available: Member and Admin. A helper line clarifies that admins can manage organization settings and invite users.
Send Invitations - A button labeled "Send N Invitations" that triggers the batch. While sending, the button shows a loading state.
Each invited user receives an email with a link to sign in and join your organization with the role you assigned.
Last updated