Allow authorized users to be able to temporarily disable project users
Nobody has claimed this yet.
- Dominant language
- Elixir
- Stars
- 296
- Forks
- 86
- Avg merge
- 1d 13h
- Merged PRs (30d)
- 50
Description
This feature should be available at two levels: Project and Instance
At a project Level:
In some situations, a project admin/owner does not want to remove a user entirely (because they may want to add them back quickly, with the same permissions) but would want to temporarily block their access to a project. This is a very useful case when a consultant is hired to work on a project. In this case, as a project owner/admin, I'd love to be able to restrict a user in a project so that they will not be able to access the project. When the disabled project user tries to access the project, they should get a notification that "your access to this project has been disabled. Please contact the project owner or admin".
At an instance level:
A sudo should be able to restrict a user's access to an instance so that they cannot log into the system. Right now, we have an disabled field on the user model exists, but the button is not properly labeled. (See image.) When a restricted user tries to log in, they should get a message that says "You no longer have access to this instance. Contact your instance admin."
The initial request here is to use the word "disable," but we already have a user in a disabled state in the application.
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by tracing the existing user model's disabled field, the current instance-login checks, and the project access checks. Review how the restriction control is labeled and how access-denied messages are presented. Done means authorized users can temporarily restrict access at both project and instance levels, with the specified messages and without removing permissions.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- elixir
- Domain
- authentication, authorization, backend
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 25/100