|Note: Make sure you are logged-in and in the correct event|
The sub-organisations/teams feature (from now on "teams") allows for the creation of different groups that will have their own events listing and user management.
To further clarify the concept:
There is a Main organisation and at least a user with Superadmin role, which can only be configured by Azavista in the back-end (sysadmin interface). Only that user can create new teams and manage users across those teams and the Main organisation (the Main organisation is, in any case, not different in concept to any of the other teams).
Each one of the users created can have different roles: Administrator (can manage users within the team for which (s)he is an admin), Event supervisor (can create events), Even planner (cannot create events but can operate within the events (s)he has permission to).
We will not cover the two remaining roles here ("Travel agent" and "Event analyst").
Follow the steps below to better understand this feature.
Log-in as the Superadmin (remember that it can only be created by Azavista).
You will arrive to the following screen in which you will be able to search among the list of teams, edit them, access the users for each one of them, and also add new teams.
As you can see in the screenshot above, at the moment there is only the Main organisation MyDemoOrg.
Let's create a new team:
As you can see, as soon as the new team is created, it is added to the list.
If we click on "edit" we will be taken to the profile page for the team where we can add new users.
New users can also be added if I had clicked on "users" instead of "edit". The advantage of the interface below is that I can easily search among users.
We will add a user with role Administrator. Notice that you can send him/her an activation link so that they can set-up the password themselves.
Now, the Superadmin user that we've been using so far can go on to create more users for this team or more teams and the users within those. But the newly created Administrator can also add users, except that only for the team (s)he belongs to (Team A1).
If the new Administrator is also added to other teams as an Administrator ((s)he could have different roles per team), then (s)he will be able to add users in those other teams.
Whenever an existing user is added to the new team, the information is pre-filled based on the inputed email address. In the screenshot below, our newly created user admin@teamA1.com is also being added to the Main organisation MyDemoOrg, only that this time (s)he is an Event Supervisor:
And now in MyDemoOrg I have:
A user will only be able to see the events for the teams (s)he belongs to. This also applies for the Superadmin.
If, in the example we've been constructing, I were to create an event in Team A1, the Superadmin wouldn't be able to see it until he adds himself (or is added by the Administrator) to Team A1.
The same situation applies for any other user.
Furthermore, any single event can belong to one and only one team or to the Main organisation (which, as clarified before, is just another team).
Whenever a user, that because of his/her roles can create events in more than one team, creates an event (s)he will have to select the team that the event belongs to.
In the screenshot above, the user we created (admin@teamA1) is logged in and creating an event. (S)he can see both of those options in that dropdown because (s)he is an Administrator in Team A1 and an Event supervisor in MyDemoOrg. Both roles allow for the creation of events and that is why (s)he has to choose to which team the event belongs to.
As soon as the event is created, if (s)he goes back to edit it, (s)he will have the option of switching it to another team.
(S)he will also be allowed to add co-owners only once the event is created/saved after a team has been chosen.
Finally, as clarified before, the events list is filtered according to the team(s) a user belongs to. Following on our example, the Superadmin can now see the event that was created in MyDemoOrg (regardless of him/her being a co-owner in it).
If the Superadmin adds him/herself to Team A1 (or is added by the Administrator), then (s)he will be able to see a combined events list: