How to limit project visibility to assigned resources
Native access control options often lack the flexibility to hide projects from everyone except the assigned resources. This limitation prevents teams from securing sensitive workflows and forces them to expose work items to unauthorized users across the workspace.
Overview
People affected2 accounts across 1 forum
Workarounds found4 items attempted
Community agreement7 total upvotes
What people tried
Every workaround mentioned in the threads below. We haven’t tested any of them — and nobody here is claiming they worked.
4 items+ Contribute
Found another way around this?
Share your steps and trade-offs so fellow engineers don't have to reinvent the wheel. No account required.
- 1Using the sales team feature at the customer levelDid this help you?
- 2Writing custom scripts or automationDid this help you?
- 3Moving project tracking and timekeeping out of the systemDid this help you?
- 4Assigning users a specific project center roleDid this help you?
Tried another approach not listed above?+ Share your workaround ↑
In their words
Unedited, grouped by where they were said, most upvoted first within each place, each linked to the thread it came from.
Where this came up
People with this problem also raised
- 3Why won't senior staff let junior admins do anything?
- 8How to get deliverables from teams you don't manage
- 2How to block public IP access for RDP while keeping VPN access
- 10How to handle wedding guest list additions at the last minute
- 3Is it okay to invite some kids to a wedding but not others?
- 3How to decide who gets access to workplace AI tools