Before you begin
Network is designed to connect and streamline operations across organizations with multiple locations. It links a parent organization to as many child organizations (branches) as it operates. Parent organizations have a yellow banner to distinguish them from regular Amilia SmartRec stores.
In this article:
1. Types of Administrator Permissions
Permission groups are sets of rules that define the level of access a user (usually a team member or volunteer) has in Amilia SmartRec. Instead of setting permissions for each person individually, you assign them to a group that already has the right permissions for their role.
When you use centralized permission management, you can configure permission groups for the parent (association headquarters) as well as separate permission groups to be used by all child organizations (branches).
✅Centralized permission management must be enabled for your organization by an Amilia employee.
2. Configuring Permission Groups for the Parent Organization
Go to Account > Administrators.
Note the two different tabs: Parent organization and Child organizations.
Click Manage permission groups, then select the Parent Organization tab.
Type a name for the permission group and click Add.
The permission group will be added to the list of permission groups. To edit the permissions, click the pencil icon.
Check off the permissions you would like to include in the permission group. You will see the notification below.
If you click Continue, the permissions will automatically be updated. Check off Do not show again, if you don’t need to see this warning in the future.
To delete a permission group, you must first reassign any administrators within it to a new one. You can't delete a permission group if someone is assigned to it. Then, click the X next to the one you’d like to delete.
2.1 Administrator Permissions Descriptions
Below is a description of each permission available at the parent-level as well as some considerations when activating them for a team member at your organization.
⚠️We are working to add new permissions related to these features and will update this table as they become available.
Permission | Description | Considerations |
Programs and activities |
|
|
View programs and activities | Access to view programs, activities, and private lessons, including their respective settings. | If the administrator only has this permission, they will not be able to create nor edit any programs or activities configured at the parent-level. They will only be able to see them. |
Activity templates | Access to view, create, edit and delete activity templates. | If an administrator makes changes to programs or activity templates at the parent-level, these changes will not be reflected in the activities that child. organizations have already imported. The child organization would need to import the activity template again for the changes to be reflected at their branch. |
Manage Programs | Access to create, edit, and archive programs as well as the ability to import, duplicate, or delete activities within a program or change program orders in your store. |
|
Memberships |
|
|
View Memberships | Access to view memberships and their respective members. | If the administrator only has this permission, they will not be able to edit memberships configured at the parent-level. They will only be able to see them.
|
Manage membership configurations | Access to create and edit membership configurations. | When using Network, memberships for all child locations are created and managed by the parent organization. If an administrator makes changes to memberships at the parent-level, these changes will be reflected in the memberships that child organizations have already imported. |
Organization settings |
|
|
General information | Access to edit basic organization information including description, logo, and more. | We recommend that only account owners and super admins have access to this permission as this information shouldn’t change often. |
Organization settings | Access to edit organization settings including calendar, tags, and other options. | When network tags are assigned to accounts/people, they will be visible on the client’s profile across the entire network regardless of the branch that you're in. They are available to be used on memberships set up by the Parent organization. |
Billing and sales | Access to view billing information and edit sales and accounting options. |
|
View administrator list and permission settings | Access to view the administrator list and the access they have. | Administrators with this permission can view the administrator lists for the parent and child organizations and their assigned groups, but cannot create, edit, or delete them. |
Manage administrator list | Access to add, edit administrators. | Keep in mind that when someone has these permissions, they manage them across your organization at the parent and child levels. |
Manage permissions | Access to create, edit and delete permission groups and their associated permission settings. |
|
Analytics (if SmartRec Analytics is enabled) |
|
|
Dashboard | Access to view analytics dashboard | Administrators with this permission can view data about your organization’s sales, enrollment, memberships, retention, self-service, and demographics. |
2.2 Suggested Parent Organization Administrator Permission Groups
Not sure where to start setting up your permission groups? We suggest configuring the following groups at your parent organization. Feel free to adjust or omit any of these if they don’t make sense for your organization!
Suggested Name | Permissions | Who should have it? |
Super Admin | All | It's a good idea to identify 2-3 people in your organization that will have the equivalent of the Account Owner permissions. This way, you’ll have backups in case of time off or if someone leaves your organization. |
SmartRec Admin |
| Depending on the number of branches in your organization and the amount of new or seasonal hires you anticipate having on a regular basis, you may want to designate a SmartRec admin who is responsible for adding administrators and assigning permission groups. |
Program Director or Program Manager |
| This set of permissions allows the person managing your programs and activity templates to create, edit, and delete them, and view data about their performance.
They can also share programs and activity templates with child organizations and determine whether child organizations can edit the fields in the templates.
You may also optionally want them to be able to edit or add tags to be used across your organization.
|
Memberships Director |
| This set of permissions allows the person who manages memberships at your organization to create, edit, and delete them, and view data about their performance.
They can also share memberships with child organizations.
You may also optionally want them to be able to edit or add tags to be used across your organization. |
Accounting or Finance Director |
| This set of permissions allows the administrator to see information about billing, sales, and analytics. |
Read-only or View-only |
| An administrator with this set of permissions can view information and analytics, but cannot create, edit, or delete anything.
|
3. Configuring Permission Groups for Child Organizations
The process to create permission groups for child organizations (branches) is similar to configuring them for the parent (association headquarters). Keep in mind that these permission groups should reflect the different roles and responsibilities at the branch level.
🎗️Administrators at your child organizations will be able to view the list of administrators and the permission groups at their branch if they have the “View administrator list and permission settings” permission. However, they will not be able to add administrators or make any edits. Notice that all actions are greyed out.
From the Parent Organization, go to Account > Administrators.
This time, click Manage permission groups and select the Child organizations tab.
Type a name for the permission group and click Add.
The permission group will be added to the list of permission groups. To edit the permissions, click the pencil icon.
Check off the permissions you would like to include in the permission group. You will receive the same notification as above. If you click Continue, the permissions will automatically be updated. Check off Do not show again, if you would not like to see this warning in the future.
To delete a permission group, you must first reassign any administrators within it to a new permission group. SmartRec will not allow you to delete a permission group if someone is assigned to it. Then, click the X next to the one you’d like to delete.
4. Adding New Administrators and Assigning Them to a Permission Group
To add a new administrator to the parent or child organization, click Administrators > New Administrator.
Fill in their information and ensure their status is set as Active.
Assign them the appropriate permission group at the parent or child organization(s). If needed, you can assign them to a permission group at multiple child locations. When you’re finished, click Save.
If the person already has an Amilia account, they’ll automatically be added to the list of administrators for the parent organization and/or child organizations that you selected. If they do not already have an Amilia account, they will receive an account activation email and must follow the link to activate it.
In the example below, Marcus Mathews was added as an administrator for Bellingsford YMCA, which is a child organization. He appears in the list of administrators in the child organizations tab.
He will see the tile to manage this organization in the Home tab on his Personal Account.
⚠️When your organization has centralized permissions, you can't add administrators from a child organization. The button will be greyed out.
FAQ
1. What’s the difference between having centralized permissions and not?
When you use centralized permission management, you can configure permission groups for the parent (association headquarters) as well as separate permission groups to be used by all child organizations (branches). Child organizations cannot add their own administrators. All administrators and permission groups are managed by the parent organization.