Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Limit abilities based on roles and responsibilities #662

Open
4 of 5 tasks
tibetsprague opened this issue Sep 7, 2023 · 1 comment
Open
4 of 5 tasks

Limit abilities based on roles and responsibilities #662

tibetsprague opened this issue Sep 7, 2023 · 1 comment
Assignees
Milestone

Comments

@tibetsprague
Copy link
Contributor

tibetsprague commented Sep 7, 2023

https://www.figma.com/file/jaHPBbpLu2Pbiywr3Y1inx/Roles-%26-Responsibilities?type=design&node-id=1-2&mode=design&t=DTA7UBeNKer3zW9B-0

Make sure users can only access and use features of the app based on the roles and responsibilities they have.

  • Show responsibilities connected to people's roles
  • Only let Administrators access Group settings (should already be working through webview)
  • Let people with add members responsibility access the invite page
  • Let people with the remove members remove members
  • Let people with the remove content responsibility moderate content
@thomasgwatson
Copy link
Contributor

As I'm picking through this, noting:

  • The figma has no mobile screens or designs, as a consequence...
  • "Show responsibilities connected to people's roles" has no easily interpretable outcome.

Everything else should be straight-forward from a UI/UX perspective.

@lorenjohnson lorenjohnson modified the milestones: HyloApp 5.6.0, HyloApp 5.5.4 Jun 18, 2024
@lorenjohnson lorenjohnson changed the title Limit abilities based on roles and responsibilities DRAFT: Limit abilities based on roles and responsibilities Jul 10, 2024
@thomasgwatson thomasgwatson changed the title DRAFT: Limit abilities based on roles and responsibilities Limit abilities based on roles and responsibilities Jul 11, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging a pull request may close this issue.

3 participants