Stitchflow
Nooks logo

Nooks User Management Guide

Manual workflow

How to add, remove, and manage users with operational caveats that matter in production.

UpdatedMar 18, 2026

Summary and recommendation

Nooks user management can be run manually, but complexity usually increases with role models, licensing gates, and offboarding dependencies. This guide gives the exact mechanics and where automation has the biggest impact.

Nooks is an AI-powered sales engagement platform built around an AI dialer, call coaching, and a virtual sales floor.

It targets revenue teams that run high-volume outbound calling.

Native SCIM 2.0 provisioning is available, but only on a Custom enterprise plan negotiated directly with Nooks sales.

Quick facts

Admin console pathSettings / Administration > Users and Roles (exact labels vary by tenant)
SCIM availableYes
SCIM tier requiredCustom
SSO prerequisiteNo

User types and roles

Role Permissions Cannot do Plan required Seat cost Watch out for
Admin Can manage tenant settings, integrations, and user access. Cannot grant capabilities outside the features enabled for the tenant. Detailed built-in role names are not fully documented publicly.
Standard User Can use the core product features exposed to their assigned role. May not be able to manage tenant settings, integrations, or other users. Exact privileges can vary by tenant configuration and contract scope.

Permission model

  • Model type: role-based
  • Description: Nooks appears to use role-based access for tenant administration and general product use, but the detailed permission matrix is not publicly documented in full.
  • Custom roles: Unknown
  • Custom roles plan: Not documented
  • Granularity: Expect administrative access to be separated from standard user access, with exact scopes configured per tenant.

How to add users

  1. Log in as an administrator.
  2. Open settings or administration and navigate to users.
  3. Choose the add or invite user action.
  4. Enter the user's work email and assign the appropriate role.
  5. Save the user and complete any activation or SSO steps required by the tenant.

Required fields: Work email address, Role

Watch out for:

  • Public documentation for user administration is limited, so exact labels may vary by tenant.
  • If SSO is enabled, upstream IdP assignment may still be required before the user can sign in.
Bulk option Availability Notes
CSV import Unknown Not documented
Domain whitelisting Unknown Automatic domain-based user add
IdP provisioning Yes Custom

How to remove or deactivate users

  • Can delete users: Unknown
  • Delete/deactivate behavior: Public docs do not clearly document whether users are disabled, deleted, or both. Treat lifecycle behavior as tenant-specific unless confirmed in-product.
  1. Open the users area as an administrator.
  2. Locate the user to offboard.
  3. Disable, revoke, or remove the account using the controls available in that tenant.
  4. Review any integrations, service accounts, or credentials associated with the departing user.
Data impact Behavior
Owned records Tenant data remains in the workspace; public docs do not describe user-owned content semantics in detail.
Shared content Shared content and workspace records typically remain available unless separately removed or reassigned.
Integrations Review service credentials, workflow ownership, and integrations separately during admin offboarding.
License freed Seat reuse behavior is contract-dependent and not publicly documented in detail.

Watch out for:

  • Offboarding should include token, integration, and service-account review, not just interactive login removal.

License and seat management

Seat type Includes Cost
Full seat Access to AI dialer, call coaching, and sales floor features; exact entitlements not publicly documented. ~$4,000–$5,000/user/year (unverified estimate from third-party sources; official pricing requires direct sales contact)
  • Where to check usage: Settings / Administration > Users and Roles
  • How to identify unused seats: Review the tenant user list and any visible login or activity metadata. No public unused-seat report was verified.
  • Billing notes: Nooks does not publish plan tiers or seat pricing publicly. All pricing is negotiated via sales. SCIM provisioning is available on Custom plans.

The cost of manual management

Because Nooks does not publish plan tiers or seat counts publicly, admins have no self-serve way to audit who holds a seat or whether that seat is actively used. Third-party estimates place full-seat cost at roughly $4,000–$5,000 per user per year, though official figures require a direct sales conversation.

Without automated provisioning, every app in your stack that depends on accurate Nooks membership data must be reconciled by hand - a process that compounds quickly across onboarding, role changes, and offboarding cycles. Limited self-serve admin controls, noted by reviewers, make it harder to identify and reclaim unused seats between contract reviews.

The decision

Manual provisioning is a workable starting point if your Nooks headcount is small and stable. Once seat counts grow or turnover increases, the absence of a published admin console path and the lack of documented self-serve usage reporting make manual management increasingly error-prone.

SCIM on a Custom plan is the practical path to keeping every app in your identity stack synchronized with Nooks membership without per-change manual effort.

Bottom line

Nooks delivers AI dialer and call coaching capabilities at an enterprise price point with no public self-serve admin documentation. Manual provisioning is feasible at small scale but carries real audit risk given opaque pricing, undocumented admin console paths, and no published usage-reporting tooling.

Teams that need reliable joiner-mover-leaver coverage across every app should treat SCIM enablement - negotiated as part of the Custom contract - as a prerequisite rather than an afterthought.

Automate Nooks workflows without one-off scripts

Stitchflow builds and maintains end-to-end IT automation across your SaaS stack, including apps without APIs. Built for exactly how your company works, with human approvals where they matter.

Every app coverage, including apps without APIs
60+ app integrations plus browser automation for apps without APIs
IT graph reconciliation across apps and your IdP
Less than a week to launch, maintained as APIs and admin consoles change
SOC 2 Type II. ~2 hours of your team's time

UpdatedMar 18, 2026

* Details sourced from official product documentation and admin references.

Keep exploring

Related apps

AdRoll logo

AdRoll

Manual Only
AutomationNot Supported
Last updatedMar 2026

AdRoll's user management is handled through Settings > Company > User Permissions. Only Admins can add, edit, or remove users — General Users cannot manage teammates or access billing by default. AdRoll offers unlimited user seats, so there is no docum

Ahrefs logo

Ahrefs

Manual Only
AutomationNot Supported
Last updatedFeb 2026

Ahrefs provides a four-tier workspace access model — Owner, Admin, Member, and Guest — governed by workspace-level roles combined with per-object share settings. Every app in your stack that handles SEO data access should have a clear offboarding path;

Atlassian Loom logo

Atlassian Loom

Manual Only
AutomationNot Supported
Last updatedFeb 2026

Atlassian Loom uses a fixed, workspace-scoped role model: Admin, Creator (also called Member on legacy Enterprise contracts), Creator Lite (deprecated for new users after February 2026), and Viewer (Education plans only). There are no custom roles or p