Feature Request: Time Tracking Permissions
Maintainers usually reply within 1 day
Nobody has claimed this yet.
Assessment
- Difficulty
- 5/5
- Estimated time
- Over a week
- Newbie friendliness
- 22/100
- Issue type
- Feature
- Clarity
- Mostly clear
- Activity status
- Active
- Domain
- authorization
Research direction
The request is about restricting what users see in the Time & Projects feature, including organization details, projects, and customers in time reports. Start by reading issue #300, which the author says covers workspace permissions, and check how the existing permission checks are applied on the server. Before any code, the maintainers need to choose between Option 1 (a system-level permission for the whole feature) and Option 2 (per-user visibility of assigned organizations). Done means the chosen option is agreed and server-side checks block the data, not only the UI.
Written by the indexing model from the issue text.
Description
Issue
When you add a user, regardless of their permissions, they can see all configuration in the time tracking time and projects feature. This has the potential to leak sensitive information (such as the hourly rate) when using Windshift as a tenanted system with multiple clients accessing the admin to view work status. I know that https://github.com/Windshiftapp/core/issues/300 resolves the issues around permissions for workspaces, however that Is not the only place that sensitive information could be viewed.
Current Behaviour
- Every user can see see all organization details and all projects
- Every user can see all customers in the time tracking reports
Desired Behaviour
The ability to secure the sensitive information in the Time & Projects feature whether that be through feature restrictions or sub-feature permissions.
Option 1:
- Add in general system permissions to restrict access and visibility to Time & Projects to even see it
- Access permissions should be validated server-side to ensure data isn't leaked
Option 2:
- Add in sub feature permissions to only allowed users see assigned organizations
- Access permissions should be validated server-side to ensure data isn't leaked
Benefits:
This would help make it so that you can invite clients to collaborate on a workspace, but restrict details in the rest of the application that may leak information about other clients and projects and would enhance other permission controls. Option 1 seems like it would be the easiest to implement, as not ever user needs to log or review time, and would make the tool more friendly to direct client collaboration on a workspace.
- Dominant language
- Go
- Stars
- 421
- Forks
- 50
- Avg merge
- 17h 34m
- Merged PRs (30d)
- 80
Getting set up
- Ships a Dockerfile or Docker Compose file
- No pull request template
- Read the contributing guide
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.
More from Windshiftapp/core
-
Difficulty 2/5 1-3 hours Newbie friendliness 66/100
Windshiftapp/core#542 ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 64/100
Windshiftapp/core#334 · 2 comments ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
Windshiftapp/core#259 · 1 comment · 1 reaction ·
Maintainers usually reply within 1 day
-
[Bug][AI chat] Select menu dont appear when on index pagePossibly taken @valentimarco claimed this today. Open
Difficulty 2/5 1-3 hours Newbie friendliness 20/100
Windshiftapp/core#541 ·
Maintainers usually reply within 1 day
-
Difficulty 3/5 1-2 days Newbie friendliness 45/100
Windshiftapp/core#538 · 1 reaction ·
Maintainers usually reply within 1 day
All issues in Windshiftapp/core
Similar issues
-
good first issue help wanted javascript
Difficulty 2/5 1-3 hours Newbie friendliness 90/100
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 64/100
fullsend-ai/fullsend#9733 · 1 comment · 1 reaction ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
karmada-io/karmada#8101 ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 88/100
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 76/100
Maintainers usually reply within 1 day