Homepage | About EASA | Contact
EASA uses User Groups and EASAP Categories to allow a User to:
Access control is implemented on an EASA System by classifying a User or an EASAP in three possible ways:
Assign an EASAP to one or more CATEGORY in one of two ways:
These new Categories will become available in the Users and User Groups pages, below.
An EASA system comes configured with two default User accounts:
These correspond to the EASA 'roles' of Author and Administrator, respectively.
An Author is a person that will design, build, test and eventually Publish an EASAP using the Builder interface and the browser-accessible 'EASA web pages'. These actions are available in Author-mode on the EASA web pages. The EASA license limits the number of Authors.
An Administrator is a person who will take care of administrative tasks which may include database configuration, access control, license management, security monitoring, resource allocation, etc. These actions are available in Administrator-mode on the EASA web pages. The EASA license does not limit the number of Administrator accounts, but for practical reasons, access should be limited to a few Administrators.
The author account is configured to allow Author and Administrator access.
To configure a User go to the EASA web pages and login as author or admin.
Set mode to Administrator:
Continue to:
Displayed on the Users tab are the default and new added Users.
Next to the User Management heading a drop down menu contains the following options:
Check boxes allow or disallow Author or Administrator privilege for each User.
Follow the steps below to change the default password for admin and author:
To configure User Groups, login as an Administrator and go to the page:
This table shows the binding between one or more EASAP Categories and the User Group to which they are available.
A User Group identifies Users who may:
Buttons below the table allow:
There is a special User Group called 'All Categories' which includes all published EASAPs.
An Author may discover and utilize a User's User Group using a CONTACT DETAILS object. One User Group may have more authorization and be able to access greater functionality than another.