Difference between revisions of "Setup"
(→Setup - Groups) |
(→Registration) |
||
| Line 14: | Line 14: | ||
==[[Registration]]== | ==[[Registration]]== | ||
| + | ===Accepted Emails=== | ||
| + | ===University ID Setup=== | ||
| + | ===Registration and Access=== | ||
| + | ===Library Card Regex=== | ||
| + | ===Support Details=== | ||
==[[Questionnaire]]== | ==[[Questionnaire]]== | ||
Revision as of 08:23, 28 July 2017
Due to the depth that each of these sections can cover, and the fact that some of these have sub-pages even further still, we will use this screen only to provide a summary of what each one is for, and by clicking the heading you will be taken to a page with content specific to each setup item.
Contents
Setup - Groups
This section contains all of the Settings for Groups within UnionCloud, it includes but is not limited to;
- Updated Group Types
- Updating Group Categories
- Setting Global Membership Expiry Dates
- Toggling visibility of Deactivated groups
For the full page on Group Settings, click here.
Group Types
Group Categories
Membership
Deactivated Groups
Registration
Accepted Emails
University ID Setup
Registration and Access
Library Card Regex
Support Details
Questionnaire
Setup - Event
Emails
Messages
Advertisements
Developers
Profile Updates
CMS
Finance
Nominal Code
Job Shop
Social Media
EVoting
RSS Feeds
Tribes
For a later release.
Permissions
Programmes
Multiple Programme Management
Previously a user was by default able to store multiple programme memberships, UnionCloud was designed this way to cater to Universities where students Study Joint Honors and are added to multiple programme codes, and also to cater to colleges where a user is likely to have multiple different courses. An outcome of this was that if an institution sent an updated Student upload file, which included a new Course, say for example a student has changed course, it doesn't instinctively remove the user from the previous course. If an institution wished to end a users programme membership, they needed to update to expire it.
This caused problems as not all institutions sent data to expire users. As a solution we have added an option to Setup which allows Unions to restrict program membership to one program per user, meaning if this option is selected and a user is uploaded with a new programme membership, it will auto expire their previous one and replace it with this one. It can be found at
You can find this page on your own site at url: <yoursite>/administrator/unions/programmes_configuration
Or Dashboard >> Admin >> Setup >> Programmes
