en/publishers/permissions.md

+## How to Manage Access to your Excercises
+
+The Sharing Plattform reflects the read permissions of your Gitlab project for each exercise.
+
+I.e. all users that can view your project in GitLab, will also view the respective exercise in the sharing plattform.
+
+As a basic rule of thumb: A **public** project can be seen by every user of the Sharing Platform. A **private** project can only be seen by users authenticated on the plattform with the respective gitlab access rights.
+
+### Default access rules
+
+We maintain two standard groups:
+ - **teacher**: This group contains all users, which have been verified as a teacher for computer science, or belongs to the CodeAbility project staff
+ - **unauthorizedTeacher**: This group contains users, that claim to be teacher, however we were not able to verify this.
+
+It is up to each project partner to set default access rights for his main group. At the University of Innsbruck, we give on the uppermost level guest access to all teachers:
+![image](uploads/10ae908b065cc69d5c22adf7e2c7ae51/image.png)
+and maintenance rights to all project members:
+![image](uploads/3022c0da0d341e706bf957f34317138e/image.png)
+Since access rights cannot be withdrawn on lower levels, please get in touch with your local gitlab maintainer for an appropriate solution.
+
+### Enforce Public Visibility for Private Projects
+
+Quite often it is the case, that you want to make your project publicly visibile, but want to make the included solution only to a limited audience. To this end you can provide a special entry _publicVisibility:_ in your metadata file, that lists specific exceptions that should not be disclosed to the public. E.g.
+```yaml
+...
+publicVisibility:
+    except:
+        - "solution"
+...
+```
+will make all files available with the exception of all files and folders that start with {solution}.
\ No newline at end of file