<div dir="ltr">From a security perspective you definitely want to create a distinct user account for each user. What if a user leaves your organisation? Will you update the password and have to communicate it to everyone before they can do further work? That's more cumbersome than doing it right from the start.<div><br></div><div>After a while you may also discover that some users will need different rights.</div><div><br></div><div>Jo</div></div><br><div class="gmail_quote"><div dir="ltr" class="gmail_attr">On Sat, Apr 25, 2020 at 12:23 PM Michael Dufty <<a href="mailto:MDufty@mbsenvironmental.com.au">MDufty@mbsenvironmental.com.au</a>> wrote:<br></div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">
<div lang="EN-AU">
<div class="gmail-m_9151806603870562456WordSection1">
<p class="MsoNormal">I’m looking at setting up a postGIS server for use to store mapping files to use with QGIS.<u></u><u></u></p>
<p class="MsoNormal">We have about a dozen users who will all need to be able to edit layers and save new layers to the server, and any new layers they create need to be editable by other users.<u></u><u></u></p>
<p class="MsoNormal"><u></u> <u></u></p>
<p class="MsoNormal">Can anyone advise if having everyone use the same user account would be a good idea? Since everyone will have the same privileges this would seem to simplify setup. Often there will be different people editing the same QGIS project at
different times, and I think it would help with that, although it looks like we would need to use the same id for the authentication on every computer if we don’t want password prompts all the time. I’m just concerned this may cause issues with the server
if the same user account is accessing the database from different locations at the same time.<u></u><u></u></p>
<p class="MsoNormal"><u></u> <u></u></p>
<p class="MsoNormal">As I understand it the alternative would be to create a role that all accounts are members of, and alter the default privileges for each account so the role gets access to any new tables created, which would be a bit of a pain to set up
for lots of accounts, but probably OK.<u></u><u></u></p>
<p class="MsoNormal"><u></u> <u></u></p>
<p class="MsoNormal">I have struggled with this in the past, and the consultant who set up a similar server for us in the past to use with Manifold gave up on getting permissions to work and just made every account a superuser. This doesn’t seem ideal, but
hasn’t caused any issues in over 10 years.<u></u><u></u></p>
<p class="MsoNormal"><u></u> <u></u></p>
<p class="MsoNormal"><u></u> <u></u></p>
<p class="MsoNormal"><b><span style="color:rgb(31,73,125)">Michael Dufty</span></b><span style="color:rgb(31,73,125)"><u></u><u></u></span></p>
<p class="MsoNormal"><u></u> <u></u></p>
</div>
</div>
_______________________________________________<br>
Qgis-user mailing list<br>
<a href="mailto:Qgis-user@lists.osgeo.org" target="_blank">Qgis-user@lists.osgeo.org</a><br>
List info: <a href="https://lists.osgeo.org/mailman/listinfo/qgis-user" rel="noreferrer" target="_blank">https://lists.osgeo.org/mailman/listinfo/qgis-user</a><br>
Unsubscribe: <a href="https://lists.osgeo.org/mailman/listinfo/qgis-user" rel="noreferrer" target="_blank">https://lists.osgeo.org/mailman/listinfo/qgis-user</a></blockquote></div>