Roles define the permissions users have.
A role gives access or limits the access (permissions) a user has within infoodle. The level of permission you give someone is based on their function, position, and trust levels. E.g. more permissions to staff and less to volunteers. Only your infoodle administrator is responsible for setting up role permissions.
The role screen shows a long series of checkboxes broken up into the modules infoodle has available. This reflects the hierarchical nature of permissions, e.g. to edit people, you first need to be able to search for them.
Examples of infoodle roles:
- Administrator
- Finance administrator
- Team leader
- Community member
See examples of role permissions for a low-level and mid-level user
Preset Roles
Every infoodle site starts with a main administrator Role set. The administrator role is designed for a few key people to have a higher level of administration rights. Therefore, this role cannot be deleted. However, you can change the name of this role and the permissions it has.
See more on Administrator Permissions.
Limiting the infoodle Administrator Role to only 2-3 people in each organisation to protect your information. Less is more. It’s better to discover someone doesn’t have the access they need and give it to them, than having to remove someone who has had access to private data.