-
Notifications
You must be signed in to change notification settings - Fork 493
Roles and Permissions
The following document describes the various roles in OSEM and their current permissions to handle settings on the admin side of the application.
OSEM comes with role-based administration for the conferences.
Except for roles, there is also the is_admin
attribute in User model, which gives the user access everywhere.
The first user that signs up automatically becomes an admin (has the attribute is_admin enabled).
To make another user an admin:
- Use the admin panel to edit a user, and check the is_admin checkbox
- Run the command: rake user:admin['email_of_existing_user']
Roles are defined in
- app/models/ability.rb for users without a role, and in
- app/models/admin_ability.rb for users with role(s)
- You can see a user's roles in
admin/users#show
, if you have theis_admin
flag enabled. - You can see all roles, and their users, for a specific conference from
admin/roles#index
andadmin/roles#show
(Follow the link Roles found at the bottom of the left sidebar menu in admin area)
Organization administrators in OSEM are administrators of a particular organization. Being the administrator of the organization which hosts different conferences, the organization admins have the right to manage their own organization which includes all the conferences hosted by their organization. An organization itself can have multiple organization admins.
Therefore, organization admins have full access to the following parts of all conferences within their organization on the admin side:
Features | Create | Update | Show | Destroy |
---|---|---|---|---|
Organization | π* | π* | π | π* |
Conferences | π | π | π | π |
Booths | π | π | π | π |
Campaigns | π | π | π | π |
Cfps | π | π | π | π |
Comments | π | π | π | π |
Commercials | π | π | π | π |
Contacts | π | π | π | π |
Difficulty levels | π | π | π | π |
Email settings | π | π | π | π |
Event | π | π | π | π |
Event types | π | π | π | π |
Event users | π | π | π | π |
Events registrations | π | π | π | π |
Lodgings | π | π | π | π |
Payments | π | π | π | π |
Programs | π | π | π | |
Registrations | π | π | π | π |
Registration periods | π | π | π | π |
Resources | π | π | π | π |
Roles | π | π | π | π |
Rooms | π | π | π | π |
Schedules | π | π | π | π |
Splashpages | π | π | π | π |
Sponsors | π | π | π | π |
Sponsorship levels | π | π | π | π |
Subscriptions | π | π | π | π |
Targets | π | π | π | π |
Tickets | π | π | π | π |
Ticket purchases | π | π | π | π |
Tracks | π | π | π | π |
Users | ||||
User roles | π | π | π | π |
Venues | π | π | π | π |
Visits | π | π | π | π |
π* : Only for the organization(s) the user has the organization_admin role
Organizers are the people who host a particular conference. Organizers are different than organization admin as organizers are restricted to a particular conference only. A conference itself can have multiple organizers.
Organizers of a conference have full access to the following parts within their own conference on the admin side:
Features | Create | Update | Show | Destroy |
---|---|---|---|---|
Organization | π | |||
Conference | π | π | π | π |
Booths | π | π | π | π |
Campaigns | π | π | π | π |
Cfps | π | π | π | π |
Comments | π | π | π | π |
Commercials | π | π | π | π |
Contacts | π | π | π | π |
Difficulty levels | π | π | π | π |
Email settings | π | π | π | π |
Event | π | π | π | π |
Event schedules | π | π | π | π |
Event types | π | π | π | π |
Event users | π | π | π | π |
Events registrations | π | π | π | π |
Lodgings | π | π | π | π |
payments | π | π | π | π |
Programs | π | π | π | |
Registrations | π | π | π | π |
Registration periods | π | π | π | π |
Resources | π | π | π | π |
Roles | π | π | π | π |
Rooms | π | π | π | π |
Schedules | π | π | π | π |
Splashpages | π | π | π | π |
Sponsors | π | π | π | π |
Sponsorship levels | π | π | π | π |
Subscriptions | π | π | π | π |
Targets | π | π | π | π |
Tickets | π | π | π | π |
Ticket purchases | π | π | π | π |
Tracks | π | π | π | π |
Users | ||||
User roles | π | π | π | π |
Venues | π | π | π | π |
Visits | π | π | π | π |
A user with Call for papers role handles all the parts of the conference related to but not limited to hadling talks, events and schedules in the conference.
The permissions of users with CFP role on the admin side are the following (permissions apply only for the conferences, for which the users have the cfp role):
Features | Create | Update | Show | Destroy |
---|---|---|---|---|
Organization | ||||
Conference | π | |||
Campaigns | ||||
Cfps | π | π | π | π |
Comments | π | |||
Commercials | π | π | π | π |
Contacts | ||||
Difficulty levels | π | π | π | π |
Email settings | π | π | π | π |
Event | π | π | π | π |
Event schedules | π | π | π | π |
Event types | π | π | π | π |
Events registrations | π | |||
Lodgings | ||||
payments | ||||
Programs | π | π | π | |
Registrations | ||||
Registration periods | ||||
Resources | π | π | ||
Rooms | ||||
Schedules | π | π | π | π |
Splashpages | ||||
Sponsors | ||||
Sponsorship levels | ||||
Subscriptions | ||||
Targets | ||||
Tickets | ||||
Ticket purchases | ||||
Tracks | π | π | π | π |
Users | ||||
User roles | π* | π* | π | π* |
Venues |
π* : Can only add the role CfP to users Only for users wih role CFP.
It is possible to allow users to suggest, and organize, their own tracks within a conference. To do that, you can open the CfP for tracks.
Users with role track_organizer can handle all aspects of proposals that belong to a specific track, eg. accept/reject proposals, schedule them, etc. The role is assigned when a track is confirmed. (Read more about the evaluation process)
The permissions for track_organizer role are the following:
Features | Create | Update | Show | Destroy |
---|---|---|---|---|
Organization | ||||
Conference | π | |||
Booths | ||||
Campaigns | ||||
Cfps | ||||
Comments | ||||
Commercials | π** | π** | π** | π** |
Contacts | ||||
Difficulty levels | ||||
Email settings | ||||
Event | π** | π** | π** | |
Event types | ||||
Lodgings | ||||
Payments | ||||
Programs | π | |||
Registrations | ||||
Registration periods | ||||
Resources | ||||
Rooms | ||||
Schedules | π** | π** | π** | π** |
Splashpages | ||||
Sponsors | ||||
Sponsorship levels | ||||
Subscriptions | ||||
Targets | ||||
Tickets | ||||
Ticket purchases | ||||
Tracks | π** | |||
Users | ||||
User roles | π* | π* | π | π* |
Venues |
π* : Only for users wih role Track Organizer.
π** : Only if event that belongs to the track(s) of the Track Organizer
Users with info desk roles are people handling the registration part of the conference.
The following are the permissions of a user with Info Desk role for his/her own conference on the admin side:
Features | Create | Update | Show | Destroy |
---|---|---|---|---|
Organization | ||||
Conference | π | |||
Booths | ||||
Campaigns | ||||
Cfps | ||||
Comments | ||||
Commercials | ||||
Contacts | ||||
Difficulty levels | ||||
Email settings | ||||
Event | ||||
Event types | ||||
Lodgings | ||||
Payments | ||||
Programs | ||||
Registrations | π | π | π | π |
Registration periods | ||||
Resources | π | π | π | |
Rooms | ||||
Schedules | ||||
Splashpages | ||||
Sponsors | ||||
Sponsorship levels | ||||
Subscriptions | ||||
Targets | ||||
Tickets | ||||
Ticket purchases | ||||
Tracks | ||||
Users | ||||
User roles | π* | π* | π | π* |
Venues |
π* : Only for users wih role Info Desk