Summary and recommendation
Nifty 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.
Nifty is a project management platform with a two-tier, role-based permission model. Workspace-level roles (Owner, Admin, Member, Guest) govern global access, while project-level roles (Manager, Member, Viewer/Guest) govern what a user can do inside a specific project. There are no custom role builders; all permissions are tied to predefined tiers.
Every app in your stack requires a provisioning and deprovisioning workflow, and Nifty is no exception - but it handles both entirely through manual admin actions. There is no native SCIM support documented at any plan tier. Enterprise plan unlocks custom SAML SSO; Google SSO is available on Pro, and Microsoft SSO on Business.
Quick facts
| Admin console path | Workspace Settings → Members |
| Admin console URL | Official docs |
| SCIM available | No |
| SCIM tier required | Enterprise |
| SSO prerequisite | No |
User types and roles
| Role | Permissions | Cannot do | Plan required | Seat cost | Watch out for |
|---|---|---|---|---|---|
| Owner | Full control over workspace: billing, member management, all projects, all settings. Cannot be removed by other roles. | Cannot transfer ownership without explicit ownership-transfer action. | All plans (one per workspace) | Counts as a paid seat on paid plans. | Only one Owner per workspace. Ownership transfer must be initiated by the current Owner. |
| Admin | Can invite/remove members, manage workspace settings, create and manage all projects, assign roles up to Admin level. | Cannot manage billing or transfer workspace ownership. | All plans | Counts as a paid seat. | Admins can remove Members and Guests but cannot remove or demote other Admins or the Owner. |
| Member | Can be added to projects, create tasks, collaborate on content within projects they are assigned to. Can create new projects depending on plan. | Cannot access workspace-level settings, invite workspace members, or view projects they are not added to. | All plans | Counts as a paid seat. | Members only see projects they have been explicitly added to; workspace-wide visibility is not granted by default. |
| Guest | Access limited to specific projects or portfolio items they are explicitly invited to. Can comment and collaborate within those projects. | Cannot access workspace settings, other projects, or workspace-level reporting. Cannot invite other users. | Starter and above (number of free guests varies by plan; additional guests may require paid seats depending on plan terms). | Guests are included at a limited free count on some plans; beyond the free allowance they may consume paid seats. Exact guest-to-seat ratio should be verified at checkout. | Guest access is project-scoped only. Guests invited via email must accept the invitation before gaining access. Guest seat counting rules differ by plan and should be confirmed in current billing settings. |
Permission model
- Model type: role-based
- Description: Nifty uses a two-tier role-based model: workspace-level roles (Owner, Admin, Member, Guest) and project-level roles (Manager, Member, Viewer/Guest). Workspace roles govern global access; project roles govern what a user can do within a specific project. There is no fully custom role builder; permissions are tied to predefined role tiers.
- Custom roles: No
- Custom roles plan: Not documented
- Granularity: Workspace-level role assignment plus per-project role assignment. Project managers can control which workspace members are added to their project and at what project role level.
How to add users
- Navigate to Workspace Settings → Members.
- Click 'Invite Members'.
- Enter the invitee's email address (one or multiple, comma-separated).
- Select the workspace role to assign: Admin, Member, or Guest.
- Click 'Send Invite'. The invitee receives an email invitation.
- Invitee accepts the invitation and creates or logs into their Nifty account.
- Once accepted, the user appears in the Members list and can be added to individual projects.
Required fields: Email address, Workspace role selection (Admin, Member, or Guest)
Watch out for:
- Invitations expire if not accepted; a new invite must be sent if the link lapses.
- Users must have or create a Nifty account tied to the invited email address.
- Adding a user to the workspace does not automatically add them to any project; project-level addition is a separate step.
- Seat count increases immediately upon invitation acceptance, which may affect billing on the current billing cycle.
| Bulk option | Availability | Notes |
|---|---|---|
| CSV import | No | Not documented |
| Domain whitelisting | No | Automatic domain-based user add |
| IdP provisioning | Yes | Enterprise (Custom SAML SSO; Microsoft SSO available on Business and above; Google SSO on Pro and above) |
How to remove or deactivate users
- Can delete users: No
- Delete/deactivate behavior: Nifty does not permanently delete workspace members from the admin console. Removing a member deactivates their workspace access. Their historical contributions (tasks, comments, files) remain in the workspace attributed to their account. The removed user loses all access to the workspace immediately upon removal.
- Navigate to Workspace Settings → Members.
- Locate the member to remove using the member list or search.
- Click the options menu (three dots or similar) next to the member's name.
- Select 'Remove from Workspace'.
- Confirm the removal in the confirmation dialog.
- The member is immediately revoked access and removed from all projects within the workspace.
| Data impact | Behavior |
|---|---|
| Owned records | Tasks, milestones, and documents created by the removed user remain in the workspace and retain their original attribution. Ownership of those items is not automatically reassigned. |
| Shared content | Shared files and comments remain visible to remaining workspace members. The removed user's name may still appear as the author/assignee on historical records. |
| Integrations | Any personal integrations or connected accounts tied to the removed user's profile (e.g., personal calendar sync) are disconnected. Workspace-level integrations are unaffected. |
| License freed | The seat is freed upon removal and the workspace seat count decreases. Billing adjustment timing depends on the billing cycle; prorated credits may or may not apply depending on plan terms. |
Watch out for:
- Removing a member does not reassign their open tasks; admins must manually reassign tasks before or after removal to avoid orphaned work.
- A removed user can be re-invited using the same email address, which will restore their access but not necessarily their previous project memberships.
- Guests removed from a specific project lose access to that project but may retain access to other projects they were separately invited to.
License and seat management
| Seat type | Includes | Cost |
|---|---|---|
| Paid Member Seat | Full workspace access at Owner, Admin, or Member role level. Access to all projects they are added to, all collaboration features available on the subscribed plan. | Starter: $7/user/month (annual) or $12/user/month (monthly). Pro: $10/user/month (annual) or $16/user/month (monthly). Business: $16/user/month (annual) or $25/user/month (monthly). Enterprise: custom pricing. |
| Guest Seat | Project-scoped access only. Limited to projects explicitly shared with the guest. Collaboration features within those projects. | A limited number of guests may be included free depending on plan; beyond the free allowance, guests may count toward paid seats. Exact terms should be verified in current Nifty pricing documentation. |
- Where to check usage: Workspace Settings → Members (shows current member count and roles); Workspace Settings → Billing (shows seat count against plan limit and current billing details).
- How to identify unused seats: No built-in last-login or activity report is documented in the help center. Admins must manually review the Members list and cross-reference project activity to identify inactive users. No automated unused-seat detection feature is confirmed.
- Billing notes: Nifty bills per active workspace member on paid plans. Seats are counted at the workspace level, not per project. Removing a member frees the seat; the timing of billing credit depends on the plan and billing cycle. Annual plans may not prorate mid-cycle seat reductions. Add-on tools (Overview, Forms, Workload) are priced separately at $16–$20/month per add-on.
The cost of manual management
Adding a user requires navigating to Workspace Settings → Members, sending an email invite, and then separately adding the accepted user to each relevant project. These are two distinct steps - workspace membership and project membership are not linked automatically.
Removing a user revokes workspace access immediately but does not reassign their open tasks. Admins must manually audit and reassign orphaned work after every offboarding. There is no built-in last-login or activity report to surface inactive paid seats; identifying unused licenses requires manually cross-referencing the Members list against project activity.
Guest seat billing adds another layer of manual overhead: the UI does not clearly surface when a guest crosses from a free allowance into a paid seat during the invite flow, which can produce unexpected billing changes.
What IT admins are saying
Practitioners flag three recurring friction points with Nifty's access model. First, guest seat counting is opaque - the paid-versus-free threshold is not surfaced clearly during the invite flow, leading to billing surprises.
Second, member removal does not trigger automatic task reassignment, which creates cleanup work at scale. Third, the absence of any activity or last-login report makes it difficult to identify and reclaim unused paid seats without manual effort.
Teams needing more granular control also note that the four predefined roles cannot be customized, and that managing guests across multiple projects requires project-by-project access changes with no bulk tooling.
Common complaints:
- Users report confusion about when guest seats count as paid seats versus free, with the distinction not clearly surfaced in the UI during the invite flow.
- Some users note that removing a member does not automatically reassign their tasks, requiring manual cleanup that can be time-consuming on large workspaces.
- Users have reported that there is no built-in activity or last-login report to identify inactive members consuming paid seats.
- Lack of custom role creation (beyond the four predefined roles) is cited as a limitation for teams needing more granular permission control.
- Some users note that the guest permission model can be confusing when guests are invited to multiple projects, as access management must be done project by project.
The decision
Nifty's manual provisioning workflow is manageable for small, stable teams where membership changes are infrequent. The two-step add flow (workspace invite, then per-project assignment) and the lack of automated deprovisioning become proportionally more costly as headcount or project count grows.
Teams on Enterprise can reduce some risk through SAML SSO with JIT provisioning, but deprovisioning still requires a manual removal step in Nifty after revoking IdP access - there is no SCIM sync to close that gap.
Teams on Pro or Business have no SSO-based provisioning path at all beyond Google or Microsoft SSO for authentication only.
Bottom line
Nifty requires fully manual user lifecycle management at every plan tier. There is no SCIM, no automated deprovisioning, and no built-in tooling to detect inactive seats.
Every app your team uses compounds this overhead, and Nifty's lack of activity reporting means unused seats can persist undetected until a manual audit surfaces them.
Enterprise teams can partially mitigate onboarding friction with SAML SSO and JIT provisioning, but offboarding remains a manual, two-system process regardless of plan.
Automate Nifty 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.
