[p4] Admin rights
Michael Delaney
mdelaney at upromise.com
Fri Aug 8 13:55:29 PDT 2008
My understanding is this, as it related to directory
//sandbox/groups/tds/...
group a; pseudo admins; should be able to delete, create/integrate,
merge, edit
group b; normal users; should only be allowed to edit, their ability to
delete, create/integrate merge should be denied
Using the protections table, you can remove their ability to branch,
with =branch, but edit & delete are the same permission category (and I
wasn't able to find a way to remove the delete cation) so in order to
edit, you are granting them the right to delete the file.
According to
http://www.perforce.com/perforce/doc.081/manuals/p4sag/04_protect.html#1
016808
________________________________
From: Gabor Maghera [mailto:gmaghera at gmail.com]
Sent: Friday, August 08, 2008 4:47 PM
To: Michael Delaney
Cc: Cameron, Ron; perforce-user at perforce.com
Subject: Re: [p4] Admin rights
I am a bit unclear on whether the actions listed as:
* Deletion of files
* Creation/Integration of branches
* Merging branches
are ones which the user should be able to do or is excluded from doing.
I read the email as those were the activities that you want this user to
have rights to. My answer was based on that.
Gabor
On Fri, Aug 8, 2008 at 11:45 AM, Michael Delaney <mdelaney at upromise.com>
wrote:
I am not aware of a way to allow for edits but restrict deleting,
branching and integrations. Perhaps a trigger could act as a watch
against these actions but I am not sure how it would be implemented.
-----Original Message-----
From: perforce-user-bounces at perforce.com
[mailto:perforce-user-bounces at perforce.com] On Behalf Of Gabor Maghera
Sent: Friday, August 08, 2008 1:53 PM
To: Cameron, Ron
Cc: perforce-user at perforce.com
Subject: Re: [p4] Admin rights
>From what you describe, admin level is probably not required. You can
give
them write permission specified for that depot path.
Something like "write user carol.hall * //sandbox/groups/tds/..." should
work. Use the p4 protect command or P4V's admin feature.
Cheers,
Gabor
On Fri, Aug 8, 2008 at 10:35 AM, Cameron, Ron
<ron.cameron at pearson.com>wrote:
> Hi All,
>
> I had a developer ask the following:
>
> Is there a way to create an admin user for an area if Perforce
allowing
> them Admin rights? For e.g. I want to restrict the following
activities
> to admin user only -
>
> Deletion of files
>
> Creation/Integration of branches
>
> Merging branches
>
> We would want this admin user to have admin privileges only on folder
> //sandbox/groups/tds and not on other projects in the depot.
>
>
>
> Thanks,
>
> Ron Cameron
>
> _______________________________________________
> perforce-user mailing list - perforce-user at perforce.com
> http://maillist.perforce.com/mailman/listinfo/perforce-user
>
_______________________________________________
perforce-user mailing list - perforce-user at perforce.com
http://maillist.perforce.com/mailman/listinfo/perforce-user
More information about the perforce-user
mailing list