|
|
| (73 intermediate revisions by the same user not shown) |
| Line 1: |
Line 1: |
| − | Users can be created, edited and deleted one by one or created and deleted in bulk (synch).
| + | #redirect [[user management]] |
| − | | |
| − | ==Create/Edit/Delete users==
| |
| − | | |
| − | User can be created, edited and deleted from the Manage Users Screen.
| |
| − | * Create User: The 'Add a user' icon creates a user one by one by filling in all the fields. Click 'Next' to select the students associated with this user.
| |
| − | * Edit User: The 'Edit a user' icon allows changes to be made about a user or changes regarding students associated with the user.
| |
| − | * Delete User: The 'Delete selected users' icon will delete the currently selected user. Multiple users can be deleted at once by selecting the tick boxes by the user’s names and selecting 'Delete selected users'
| |
| − | | |
| − | * Users 'Activated' status can be changed by selecting the users (ticking the tick boxes next to their names or using shift- and control-clicks) and selecting the 'Activate selected users' or 'Deactivate selected users' buttons.
| |
| − | | |
| − | | |
| − | ==Synch - Create/Delete users in bulk==
| |
| − | | |
| − | Synchronising is the process which updates the user data held in Insight from either the contacts held within SIMS or from staff.
| |
| − | When performing a Parental synchronisation, from all the available contacts a student may have recorded against them, Insight will use only those that match the User Creation options in [[Preferences]].
| |
| − | *Never use email addresses for usernames when synchronising parents
| |
| − | :Email addresses can change, which could cause confusion, and additionally email addresses for external domains are not valid usernames for Active Directory purposes, so you may want to use this option to ensure everyone has similarly styled usernames.
| |
| − | *Only create users for contacts with parental responsibility
| |
| − | :Checking this option means that users will not be created for contacts without parental responsibility
| |
| − | *Only create users for contacts with Priority 1
| |
| − | :It is possibly but unusual to have more than one Priority 1 contact. Checking this option means that only Priority 1 contacts will be made into users.
| |
| − | *When considering contacts with Priority 2 or lower, only create users for non-cohabitees of the student
| |
| − | :If you are not ''only'' creating users for Priority 1 contacts, but are allowing Insight to consider lower priorities, this setting will only create a user account if the lower priority contacts do '''not''' co-habit with the student being considered. Put another way, if this setting is ON, Insight will not create accounts for contacts who live with the student.
| |
| − | *Deactivate a users links when the contact has no email in SIMS, and previously an email was found
| |
| − | :If you use the email fields for contacts in SIMS to indicate 'IT active' this setting can help you to create user accounts based on the email field having something in.
| |
| − | *Create users for contacts with court orders
| |
| − | :By default users will not be created for contacts with court orders, but this can be achieved if required by checking this option
| |
| − | | |
| − | When performing a Staff based synchronisation, all current staff will have Insight accounts created.
| |
| − | | |
| − | Depending on the synchronisation method selected, you will also have to select from these options:
| |
| − | | |
| − | *Set the new users' approved status as 'Approved'
| |
| − | :If the 'yes' option is selected then this option Activates the users account (In the Manage Users screen a tick will appear in the activated column). This status can be changed manually via the 'Activate/Deactivate selected users' buttons
| |
| − | | |
| − | *Whether to use SIMS credentials where possible for Staff users.
| |
| − | | |
| − | *The role that new users will be put into.
| |
| − | | |
| − | Once users have been added, randomly generated passwords may be exposed via [[Generated passwords]].
| |
