2,299
edits
Changes
User
,no edit summary
* Because [[Organization Terminology]] will vary between instances, remember that your specific instance may use different nomenclature for users/contacts. The related functions such as how to activate or add users in every instance will remain the same.
* '''People '''added into the system are similar to [[Organization|organizations]] in their behaviour and functionality. A person object may store information about internal staff as well as external contacts/venders. All people are also stored in a single format and table in the database, each with their own set of [[User#Standard People Fields|standard fields]].
* Each person will have a single parent organization in the [[Organization hierarchy]], though they represent a variety of users and contacts at the different organizational levels. For example, you might have '''Teaching Assistants '''and '''Professors '''at the '''Department '''level, and '''Deans '''at the '''University '''level.
As part of the contact setup process, you assign contacts "roles." A user can access and manipulate information only to the extent permitted through their membership of specific [[User Role|roles]], combined with those roles' [[Role Based Security|ability]] to manage system-wide [[Manager Permission|permissions]]. Roles therefore define user access to system resources such as the [[interfaces|interface]] they see (Administrator vs normal user portal), the [[application]]s they can access, the [[fields]] they see within each application, and the [[reports]] they can run.
