SAM V1:Permissions

From AMACWiki
Revision as of 13:17, 5 October 2010 by Alliecox (Talk | contribs) (Pre-Defined Roles)

(diff) ← Older revision | Latest revision (diff) | Newer revision → (diff)
Jump to: navigation, search

Users and Roles

In SAM V1, users are assigned to roles. Roles are used to determine what permissions are granted. Permissions regulate what data users see and what functions they can perform.

Functions include adding, editing, viewing or deleting data. For example, a role can be setup so that users in the role can view records in a table but not add records to the table.

Both table and field level permissions exist for roles. For example, a role can be setup to either deny access to an entire table with SAM V1, or deny access to select fields within a table.

Refer to the QuickBase help on roles and permissions for a more in-depth explanation.

Pre-Defined Roles

The following roles are defined in SAM V1:

Role Permissions
Administrator
  • Can add, edit, and view all fields on all records in all tables.
  • Can delete records in all tables except students and accommodation master.
  • Can add, edit, and save tables, fields, forms and views.
  • Can change a record owner.
Service Provider
  • Can add, edit, and view all fields on all records in all tables.
  • Can delete records in all tables except students and accommodation master.
Student Assistant
  • Can add, edit, and view in the students, consents, tests, orders, and class schedules tables.
  • Can add and view only in the tasks and forms tables.
  • Can view only in the disabilities, accommodations, and accommodation master tables.
  • Cannot add, edit, or view in the referrals, case notes, or documentation tables.
  • Cannot delete records in any table.
Test Proctor
  • Can add, edit, view, and delete all fields on all records in the Tests tables.
  • Can view students, accommodations, class schedules, and accommodation master tables.
  • Cannot view, add, edit, or delete in the disabilities, consents, referrals, case notes, tasks, orders, and documentation tables.

Additional Roles

Additional roles can be defined based on the permission needs defined by the customer.