##// END OF EJS Templates
integrations: refactor/cleanup + features, fixes #4181...
integrations: refactor/cleanup + features, fixes #4181 * added scopes on integrations, scopes are: - repo only - repogroup children only - root repos only - global (any repo) * integrations schemas now have separate section for the settings (eg. slack) and options (eg. scope/enabled) * added descriptions to integration types * added icons to integration types * added 'create new' integration page * added scope of integration to integrations list * added breadcrumbs for each repo/repogroup/global integrations pages * added sorting to integrations list * added pagination to integrations list * added icons to integrations list * added type filter to integrations list * added message to integrations list if none we found * added extra permissions check on integrations views * db migration from 56 => 57 - adds child_repos_only field * added tests for integrations triggered on events * added tests for integrations schemas * added tests for integrations views for repo/repogroup/admin

File last commit:

r1:854a839a default
r731:7a6d3636 default
Show More
setting-repo-perms.rst
26 lines | 880 B | text/x-rst | RstLexer
/ docs / admin / setting-repo-perms.rst

Repository Administration

Repository permissions in |RCM| can be managed in a number of different ways. This overview should give you an insight into how you could adopt particular settings for your needs:

  • Global |repo| permissions: This allows you to set the default permissions for each new |repo| created within |RCM|, see :ref:`repo-default-ref`. All |repos| created will inherit these permissions unless explicitly configured.
  • Individual |repo| permissions: To set individual |repo| permissions, see :ref:`set-repo-perms`.
  • Repository Group permissions: This allows you to define the permissions for a group, and all |repos| created within that group will inherit the same permissions.