We have described in a previous post the necessary steps for securing your Merlin projects. Pretty easily as you may already know; you either promote an existing resource to a user, or create a new resource just for the login purpose, configure its permissions in the ‘permissions’ inspector and hide your project from anonymous users.
Easy? Yes of course, but why do we mention an old post if everything is said in it? Well it’s obvious, isn’t? Â What our blog post didn’t do was to provide a short screencast of these actions.
This is done here, so sit back and enjoy the videos showing how to…:
- secure the project in Merlin, enable web sharing and access the project over the web browser
- access secured projects shared by Merlin Server
Check out our YouTube channel,  you will find there introduction videos for the ProjectWizards’ products (Merlin for Mac OS X, Merlin Server and Merlin iPhone) along with short ‘how to’s.
Pingback: Merlin – publishing projects for collaboration with other Merlin users » MacPM
Hi,
We are looking to start using Merlin2 as our project Management System for our Branch.
One of the most important aspects that we are looking for is a robust sharing methodology for our projects.
Even though we are very happy with the extensive set of options that you offer, we do have one more question regarding a particular aspect that we would really like to see and were wondering if this already possible:
Would it be possible to give each user a static / not variable password? This way each project can be run by a different Project Lead and the Lead can then restrict the privileges based solely on user names without having to give out different password for each and every project or having to share passwords in such a way that renders the concept of having a password in the first place, obsolete.
Hoping to have inform you in a sufficient manner, we will enthusiastically await your advice.
Sincerely yours,
Daniel Marquina
Hi,
To put it in an example form:
With only 3 parties involved:
Jack
Jane
Jill
How do we achieve a scenario in which each party chooses their own password (that is only known to them for each and every single project wether they are the Project Lead or not) and that the Project Lead would then only need to adjust the privileges of each member without assigning a different password for each project.
As you can imagine, the more projects that are being run simultaneously and the more users there are, the more complicated the managing of passwords becomes.
This resembles be the same principle that other databases use to administer privileges to users.
Hoping to have inform you in a sufficient manner, we will enthusiastically await your advice.
Sincerely yours,
Daniel
User and passwords are saved and handled in the Merlin projects. If you always have the same users, we would suggest to save a project template containing these resources and also their passwords. When creating a project out of this template you automatically get the same users and passwords.
Best regards, Vicky
Pingback: Merlin – secure projects and access over the iPhone or iPad app »
Pingback: Merlin – publishing projects for collaboration with other Merlin users | MacPM