Manual Session Entry is no Longer Tied to the "Edit Session Data" User Privilege
Documenting a session after the fact no longer depends on a privilege meant for something else. Any user can now enter a manual session, while the Edit Session Data privilege now controls only one thing: editing session data after it was already completed. ๐
โจ What's new:
- ๐ All users can now enter a manual sessionโ Anyone can start a manual session from the client's Home page and enter data for the first time, whether or not their role has [Edit Session Data]turned on.
- ๐ Edit Session Data now does one jobโ The privilege controls whether someone can edit session data after that session has already been completed and saved. When it is off, the Edit Session Data option is hidden from the three-dot menu on completed sessions (History > click into session > โฎ at the top of the page), meaning: they can't reopen the session once they've saved it the first time.
- ๐ Existing role limits are unchangedโ Behavior Technicians with Edit Session Data on can still edit only their own completed sessions. Supervisors and above can still edit others'.
๐ก Why it matters:
Before this change, turning Edit Session Data off for a role blocked that role from the Edit Session page entirely, so those users could not enter a manual session at all. Organizations had to choose between letting technicians change any past session or losing after-the-fact documentation for outages, missed clock-ins, make-up sessions, and payroll corrections. Those are now two separate decisions.
For now, all users can enter manual sessions.
๐
A separate privilege to control who can enter a manual session is planned as a follow-up.
---
Also in this Release
โ๏ธ A few minor design changes, and couple of bug ๐ fixes related to user profile visibility and staff profiles