User Management - How To
Add a New User
Before adding a new user, confirm what permissions the user should have (e.g., instance- district-, school- or vendor-level access; which district(s) or school(s), etc.). To ensure we are complying with FERPA, the new user should not be the person confirming their level of access, it should come from the data manager or director of the grant!
Create the User in SCRIBE
In SCRIBE, go to Tools > User Management.
Click Add.
Enter the new user’s details in the required fields, using their email address as their User Name. Leave the fields in the Status box in their default state.
Click Save.
SCRIBE will send the new user an email with a temporary password and a link to log into SCRIBE for the first time where they will be immediately prompted to set their own password. Let the new user or whoever requested the new user be added know to expect an email and to check their spam folder if they don’t see an email from SCRIBE soon.
Associate a User
If you attempt to add a new user who already exists, you will receive an error message: User Name is being used by another user. User Name must be unique. Associating a user is used when the user already has access to another instance in SCRIBE.
In SCRIBE, go to Tools > User Management.
Click Associate User.
Enter the last name or user name. Click Search.
Check the box next to the correct user. Click Associate.
Assign Roles
User roles, also referred to as user permissions, designates what data the user is able to view, enter, and/or edit in SCRIBE. Confirm with the grant’s data manager or director which permissions the user should have.
In a user’s profile, click on the Roles tab.
Click the level of permission the user needs (e.g., Instance-, District- or School-level).
Existing roles already assigned to that user at that level will be displayed, if any. Click Edit Roles.
Check the box(es) next to the appropriate permission(s).
Click Save.
Permission Levels:
System-level - reserved for Xcalibur employees only
Instance-level - allows a user to view, enter, export and/or edit data for all districts and schools in the instance. If a user has instance-level permissions, they do not need to be given district- or school-level permissions.
District-level - allows a user to view, enter, export and/or edit data for that district and all school(s) in that district. If a user has district-level permissions, they do not need to be given school-level permissions for any school in that district. Users can be given district-level permissions for multiple districts if needed.
School-level - allows a user to view, enter, export and or/edit data for a school. A user can be given school-level permissions for multiple schools in the same or different districts if needed.
Tips & Troubleshooting:
Typically, do not assign permissions that allow the user to delete any data unless explicitly requested by the data manager or director of the grant. This is a fail-safe to make sure data is not accidentally deleted or edited.
Typically, do not assign user management permissions. This is a fail-safe to make sure all users retain the permissions they were assigned originally and do not gain access to protected data or permissions to delete/edit data. Some grants have designated one staff member who has user management permissions and is responsible for adding new users to SCRIBE in which case only that person should have user management permissions.
It might be useful to assign additional permissions to a user for a limited period of time. For instance, if a user needs to edit a group of students, delete or edit services, add a group of new users to SCRIBE, etc. Ask them to notify you when they are finished so you can remove the added permissions from their account.
Vendor-level permissions allow the user to upload and download attachments at the instance level only. They cannot view any other data in SCRIBE. Vendor-level permissions are typically assigned to users who work for a GEAR UP vendor or partner (e.g., a tutoring service, texting service, etc.) and typically attach documents like attendance rosters and other service participation documentation or match data.
Sometimes a requestor will ask for a user to have the same permissions as another user in their instance. The Role Summary under the Role tab is an easy way to see what permissions the existing user has and that the new user should also have. Take a screenshot of that person’s permissions so you can reference it when you assign the new user the same permissions.
Roles Assigned in SCRIBE
*I = Instance, D = District, S = School, V = Vendor