Your data in Attendium is tightly guarded, and by default only you are allowed to access it. One of the most powerful features in Attendium is however the possibillity of giving others access to your data. By doing this, you can efficiently and safely let others share your workload which usually leads to a more efficient workflow.
This is the most fundamental concept of the permissions model. You should create users for anyone that you would like to give permissions to access your data. A user has the following properties:
- Name - display name of the user. This is what you and others will see
- Username - used to log in to the guest list app and website
- Password (optional) - used to log in to the guest list app and website
When your account is created, you are given a master user for that account. After that you can create new users for your account:
- Log in using your master account
- Go to the Users section by clicking the link in the top menu
- Click the Add guests link below the list to the left
- Enter the name and username of the new user in the form to the right
- Press Save
By default, a user does not have a password and thus can not log in. To set a password for a user, click the Change password button when viewing the user. You can at any time change the password of a user, but you can not see the existing password.
Venues, events and guest lists have a list of access permissions for users. It is here that you specify who and most importantly what they can do with your data. There are different kinds of permissions you can give users:
- View all guests - see all tickets and guests
- Add guests - add new tickets and guests
- Check in guests - use tickets, or in other words check in guests
- Administer - everything, including all of the above
Hierarchy & access permission inheritance
If a user has the permission to administer a Venue, then it is reasonable to think that the permission to administer every event for that Venue should be implied. This is what inheritance means and works with all of the access permissions above. There are three levels in this hierarchy:
- Guest list
If you give a user access permissions to a Venue, all events and guest lists under that venue will inherit those permissions. If you want fine grained permissions you can give a user permissions to a specific guest list only.
When you want to give a user access to your data, but limit it somehow, then boundaries can enable you to do that. The following boundaries can be set:
- Max tickets - the number of tickets that the user can add
- Max free tickets - the number of free tickets that the user can add
You can set these on events and guest lists, and they are not inherited.