Skip to content

GitLab

  • Projects
  • Groups
  • Snippets
  • Help
    • Loading...
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in / Register
stork
stork
  • Project overview
    • Project overview
    • Details
    • Activity
    • Releases
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
  • Issues 140
    • Issues 140
    • List
    • Boards
    • Labels
    • Service Desk
    • Milestones
  • Merge Requests 5
    • Merge Requests 5
  • Operations
    • Operations
    • Incidents
  • Packages & Registries
    • Packages & Registries
    • Container Registry
  • Analytics
    • Analytics
    • Repository
    • Value Stream
  • Wiki
    • Wiki
  • Snippets
    • Snippets
  • Members
    • Members
  • Collapse sidebar
  • Activity
  • Graph
  • Create a new issue
  • Commits
  • Issue Boards
  • ISC Open Source Projects
  • storkstork
  • Issues
  • #118

Closed
Open
Opened Dec 27, 2019 by Tomek Mrugalski@tomek🛰Owner

Role-based access, password changes should be documented

With the #97 (closed) merging soon, we need to document the user visible changes introduced:

  1. describe the idea behind role-based access
  2. explain what roles are currently available (this list is expected to grow significantly over time)
  3. update the section about creating new users (only super-admins, explain group selection)
  4. describe how a user can change his own password
Assignee
Assign to
Stork-0.4
Milestone
Stork-0.4 (Past due)
Assign milestone
Time tracking
None
Due date
None
Reference: isc-projects/stork#118