2 months ago
Hi,
From my understanding, workspace roles (admin / member / deployer) apply to all projects within a workspace. If I want to grant someone access to only a single project, the correct approach would be to add them as a project member with the “Can edit” role, rather than adding them to the workspace.
My question is: within the scope of a specific project, is a “Can edit” project member functionally equivalent to a workspace member, or even a workspace admin?
In other words, does “Can edit” provide the maximum level of permissions available at the project scope (deploys, settings, resources, etc.), just without visibility or access to other projects in the workspace?
I want to ensure the user has full control over that one project, while avoiding granting workspace-level access that would expose other projects. Are there any suggested approaches?
Thanks in advance for any clarification and suggestions.
4 Replies
2 months ago
Hey there! We've found the following might help you get unblocked faster:
If you find the answer from one of these, please let us know by solving the thread!
2 months ago
Yes thats exactly how it works!
Anybody you add only to the project will have permissions in that project only. No read/view, edit, delete, create any permissions in any other projects of the workspace.
Workspace level permissions apply to all projects.
Status changed to Awaiting User Response Railway • about 2 months ago
noahd
Yes thats exactly how it works!Anybody you add only to the project will have permissions in that project only. No read/view, edit, delete, create any permissions in any other projects of the workspace. Workspace level permissions apply to all projects.
2 months ago
Thanks for your prompt response!
But my question is: within the scope of a specific project, is a “Can edit” project member functionally equivalent to a workspace member, or even a workspace admin?
How powerful is “can edit” project member? Is “can edit” as powerful as workspace member or workspace admin within the specific project?
I am asking this because I want to give the user powerful enough permission to the specific project while don’t have to assign them as workspace member or admin (I don’t want the user to have access to other projects).
Status changed to Awaiting Railway Response Railway • about 2 months ago
hugohsieh-oecjfk
Thanks for your prompt response!But my question is: within the scope of a specific project, is a “Can edit” project member functionally equivalent to a workspace member, or even a workspace admin?How powerful is “can edit” project member? Is “can edit” as powerful as workspace member or workspace admin within the specific project?I am asking this because I want to give the user powerful enough permission to the specific project while don’t have to assign them as workspace member or admin (I don’t want the user to have access to other projects).
2 months ago
In the scope of a Project the "Can edit" permission is functionally equivalent to a workspace member yes.
My best suggestion is adding an alternate account you own as an editor to a project and investigating what scope they have and if it aligns with what you'd want the user to be able to do!
Status changed to Awaiting User Response Railway • about 2 months ago
2 months ago
This thread has been marked as solved automatically due to a lack of recent activity. Please re-open this thread or create a new one if you require further assistance. Thank you!
Status changed to Solved Railway • about 2 months ago