---
title: "Extended permissions for larger organizations"
description: "The extended permissions feature is intended for larger organizations that are divided into several units and need to handle part of the agenda separately, while at the same time keeping central oversight and control. A typical example is organizations with a more complex structure and hierarchy, such as Sokol or other large membership organizations."
url: https://help.eos.cz/en/articles/168-extended-permissions-for-larger-organizations
collection: "Permissions"
updated: 2026-11-09
language: en
alternates: [cs, pl, sk, sl]
---

# Extended permissions for larger organizations

The extended permissions feature is intended for larger organizations that are divided into several units and need to handle part of the agenda separately, while at the same time keeping central oversight and control. A typical example is organizations with a more complex structure and hierarchy, such as Sokol or other large membership organizations.

## What the feature allows

-   individual sections to operate independently,
    
-   keeping an overview and central control for the umbrella organization,
    
-   defining user permissions down to the smallest details.
    

## Prefer a video?

## **Where to start with the setup**

Extended permissions cover the following areas:

-   **Seasons** – setting active seasons for individual sports and sections
    
-   **Organizational units** – defining sections and assigning them to seasons
    
-   **Walls and communication space** – space for communication between the umbrella organization, individual sections and individual teams and their members and representatives
    
-   **Permissions** – setting rights for coaches, chairpersons and other administrators
    
-   **Member import** – bulk import of members with assignment to sections
    
-   **Bank accounts and cash registers** – assigning accounts to organizational units for payment management
    

### Seasons

Seasons determine the period in which sports sections or clubs operate. Thanks to extended permissions, several seasons can be active at the same time. Seasons affect only the sports agenda (categories, competitions, training sessions), **they have no effect on payments or the member database**. Each sport or section can therefore have its own season (e.g. from August to July, a calendar year, a term for clubs).  
  
**Module location**

Management > Settings > Seasons.

  
**Creating a new season**  
  
In the top right we choose Settings > Add new season group > Name (e.g. calendar year, school year, sports year)  
  
When all season groups are done, we close it with the cross. In the overview there is a “+” on the right for each season group, where we set the specific season.  
  
The settings include:

-   the season name (e.g. under the season group Sports year we add: 2025/2026)
    
-   the start and end of the season (e.g. 1 Aug 2025 - 31 Jul 2026)
    

### **  
Organizational units**

After creating the seasons, you need to set up the organizational units (typically sections). This is an administrative division; the members themselves will not see which Organizational units they belong to. Each member can belong to several Organizational units. Permissions can then be determined by Organizational unit, Payments assigned, and filtering done in many places in the platform.  
**  
Module location**

Management > Settings > Organizational units

  
**Creating Organizational units**  
  
In the top right we choose “+”.  
  
The settings include:

-   Name (e.g. Athletics section or Athletics)
    
-   Season group (you select from the season groups prepared in advance)
    
-   The option to add an e-mail linked to the Organizational unit for bulk messages (e.g. mailing)
    
-   Showing the Organizational unit in the registration form (applicants can select directly in the registration form which section they are applying to; according to the selected Organizational unit the request is then also shown to the administrator of the organizational unit, if they have the given permission)
    

###   
**Teams and walls ( = communication space)**

By creating teams and walls you prepare spaces in the EOS Platform for all members for communication, organizing training sessions and other events and so on. The structure is entirely up to you and it is important that it corresponds to how the organization really works.  
**  
Module location**

Management > Teams and walls  
  
**Creating Teams and walls**

  
Creating three levels of communication:

1.  **The wall of the whole organization** – it is predefined - you will always find it as Whole organization > Non-season. All registered members have access to it (regardless of the Organizational unit); it is used for centrally sharing information across the whole organization  
    
2.  **The section wall** – it needs to be created for each Organizational unit (section) separately. All members assigned to the given Organizational unit (section) then have access automatically; it is used for sharing information only with members of the given Organizational unit (section). You create it: Management > Teams and walls > “+” in the top right
    

The settings include:

-   name (e.g. Volleyball section everyone)
    
-   access: organizational unit
    
-   organizational unit: you select which section it concerns (in our example: Volleyball section)
    
-   season: you select the current one
    
-   tick: Show in the Member zone (important - otherwise members will not see it!)
    

  
   3. **The team wall** – it needs to be created for each team/group separately. Only the members you manually add to the Roster of the given team have access to it. It serves for detailed communication between the members of a specific team. You create it: Management > Teams and walls > “+” in the top right  
  
The settings include:

-   name (e.g. Volleyball U16)
    
-   access: roster
    
-   organizational unit: you select which section it concerns (in our example: Volleyball section)
    
-   season: you select the current one
    
-   tick: Show in the Member zone (important - otherwise members will not see it!)
    

### **Permissions**

Thanks to extended permissions you can define who can do what in the platform, at the level of the whole organization, individual Organizational units (sections) and directly of teams.

[

Member permissions

Define your own roles in the organization with access levels for the individual modules in the Management section. Keep track of who can read or edit what and manage all access clearly in one place.

](https://help.eos.cz/en/articles/106.md)

  
Beyond Permissions, the Extended permissions module gives you more options:

-   One person can have several different permissions
    
-   You set one Permission for the section chairperson and then set the scope only for a specific Organizational unit (section)
    

Example: Franta Novák plays football as a regular player, is at the same time the chairperson of the volleyball section and also the accountant of the whole organization. You therefore set his permissions as follows:  
You add him to the team Football Men A as a regular member (= he can respond to training sessions and reply to posts on the wall of this team). His powers are identical to those of other regular members.   
In Management > Permissions you create the permission section chairperson (you give it permissions similar to the Main administrator) - when you add Franta, you have the option to Set the scope: Whole organization, Football, Volleyball - you tick Volleyball (= Franta will have high permissions only in the Volleyball section).   
In Management > Permissions you create the permission Accountant (read and write Payments and Transactions, other tabs: no access) - when adding Franta, the Scope setting pops up again: this time you select: Whole organization (= Franta will be able to check payments and transactions across all sections, the whole organization).

### **  
Member import**

Bulk import allows you to add hundreds of members quickly:  

-   Use the table available for download: [https://help.eos.cz/en/articles/142](https://help.eos.cz/en/articles/142.md)
    
-   Mandatory columns: first name, last name, date of birth, e-mail
    
-   With extended permissions you need to add the column **Team Groups,** where you fill in the section names EXACTLY as they are in Settings > Organizational units!
    
-   After the import, each chairperson will only see their own members and can work with them
    

**Module location**  
Management > Members > More > Import

### **Bank accounts and cash registers**

-   Assigning accounts to organizational units – each unit can have its own account
    
-   If the account is shared for the whole organization, it is entered centrally (in the Organizational unit field it stays: Whole organization
    
-   Payments and prescriptions are assigned to the relevant account and organizational unit
    

**Module location**  
Management > settings > Bank accounts and cash registers

## **Recommendations**

Before using the platform with extended permissions for the first time:

-   Think through the structure of seasons, organizational units and teams
    
-   Think through the configuration of mandatory and optional data, the age limits for member and parent access
    
-   Determine the hierarchy and set permissions for individual roles - start with minimal permissions and extend them gradually
    
-   Set up the bank accounts
    
-   If you run into anything unclear, contact [support@eosclub.app](mailto:support@eosclub.app)
