Hi,
we have started using Atlas as a company-wide communication platform about goals, projects and initiatives. In the Standard plan one can create projects with a "private" attribute. This sounds reasonable due to limit the visibility of some initiatives at the beginning or at all.
My question is now: why can't I turn a initially marked as private project into a public one? This is a reasonable use case when - in the beginning - you want to limit access to a project but with time open it to the public. Archiving it is not really a good option since you loose all the information you gathered along the path like decisions, risks and insights as well as all the updates. If you want to "hide" this you always can create a new project but this is not always the case.
We would vote for this option since it is more reasonable than the other way round (make a public project private).
Thanks,
Sandro
Hi @Sandro Ruch
I am from the product team here at Atlas.
This is awesome feedback and we have received it from other customers too. I will add your input for the team to consider when they prioritise this feature.
Cheers
Any updates on this? I just run into this problem as well
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Same here.
To be honest, it wasn't really clear as to the specifics as to what 'private' and 'public' mean, so I chose private but now I think I'm lacking features that are only available in 'public' projects? I'm not really sure, but I can't risk going too far in one direction if there's no toggle to switch easily, so I guess I'll be recreating the project to find out.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
We are trying Atlas right now and would prefer a roll out with some lighthouse users but need the confidence to set it up without all eyes on it. we want to give our user the space and freedom to do errors since there is no sandbox.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Any update on this? When can we expect that this feature will be available?
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
We are just trialling Atlas and have set projects to private. Learning that we can't change them later is going to impact us.
I don't want to give everyone access to projects when they are first set up as we need to do some testing, but have to delete and recreate the project to make it public feels crazy.
Update, not being able to remove the flag when copying a project seems like an oversight. In the current structure this would be the only way to easily convert a private project over to being public.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
I agree with all the above. It should definitely be possible to change a project to public later on.
@Yerbol Nisanbayev Is there already an official ticket/feature request for this. I couldn't find any.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
I would strongly recommend that even if there is no plan to allow for this functionality, the easily overlooked warning text is made far more visible;
Consider how easily readers would miss `can't` for `can` in the following (given the fairly logical assumption that this isn't a permanent checkbox...
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.