List the actions, not just the applications
The receiving person may need to read context, update a task and record a decision. Those are different permissions. List the minimum actions required for the agreed scope. Do not assume that being added as a guest supplies every internal capability, or that a title in the organization automatically grants access to all project material.
Use documented roles carefully
Nifty’s guest documentation describes project-scoped access and limits on actions such as changing milestones or assigning tasks not created by that guest. Verify current plan and role behavior in the actual account before relying on it. This guide does not instruct you to widen access, and it does not treat guest status as a universal free replacement for an internal seat.
Keep a missing permission visible
If the receiver can read a task but cannot perform the needed update, record the exact missing capability and route it to the account owner. Continue independent authorized work where possible. Do not solve the problem by sending the outgoing person’s password, moving files into a public folder or making an unnecessary duplicate account.
Close the temporary arrangement deliberately
Agree when temporary cover should be reviewed and who owns that review. The right end action may depend on continuing responsibilities, retention rules and account configuration. Do not automatically delete a person or their records at the end of a leave period. Follow the organization’s authorized process and preserve the work history that remains necessary.
Keep the test proportionate
A read-only cover task may not need permission to alter project configuration. A task update may not require access to every workspace. Ask the authorized account owner to match the smallest suitable role to the actual action, then verify the result through the receiver’s own view. Do not create a broader role first and narrow it later merely for convenience. Record what was tested and leave unrelated permission questions outside the handover.
Sources used for this page
These records support the facts and comparisons above. Merchant-controlled records are labelled so you can separate product claims from independent evidence.
- Nifty guest permissions — Merchant documentation · help.niftypm.com · Merchant-controlled · checked 2026-10-01