John Kranz on 20. June 2009
We are often asked by users how one can secure a project they wish to publish using Web-Sharing so that the public will be unable to access it. The follow-on question to this is how permission settings can be set within a given project as well. This user tip covers both questions.
Securing a Project
In order to secure a project so that it is not accessible to anyone, please do the following.

This will protect the access rights so that the project file will not be accessible by all (public).
Permission Settings
Merlin provides a simple way to configure permission settings for those users you want to access a given project file. Here are the basic steps involved:

As you can see from the screenshot above, setting up permission rights is not only easy, but the configuration options are very flexible to meet your needs.
Tags: Merlin, Merlin 101, Permissions, Sharing
RSS feed for comments on this post. TrackBack URL
Copyright © ProjectWizards GmbH, Melle, Germany. All Rights Reserved.
If you have someone in a group that have permissions and he has a personal record with other levels of permissions, which will be the ruling situation?
May users and groups defined in one project be used in other projects? Or do the have to be redefined in each project?
Merlin 2 has no global resources, so you need to define the resources on the other projects as well.
There is a way though not to do this manually each time for new projects; You create a project, insert the resources, save the project as a template and start new projects from this template.
Best regards, Vicky
@MacJules: Members of the resource group will inherit the resource group permissions unless they were set explicitly.
You may read more about it in Merlin web help:
i am testing the Merlin server.
I would like to share projects with users, but they can see all projects that are published. Can you exlude other projects to this users ?
Peter
Hi Peter, you should not forget in this case to enable the security option: “Hide from anonymous users” (as described in the post).
This means, if you have for example 3 projects; two for user A and another for user B.
and user A and B call the URL of the server, they both see nothing at first. When user A authenticates himself, he sees his 2 projects.
And if user B authenticates himself, he sees only one (his) project.
Best Regards, Vicky