Jump to content

Search the Community

Showing results for tags 'permissions'.



More search options

  • Search By Tags

    Type tags separated by commas.
  • Search By Author

Content Type


Forums

  • Plastic SCM
    • General
    • Installation and configuration
    • Unity 3D
    • Plastic SCM on Mac
    • Plastic SCM on Linux
    • Gluon
    • Git interop
    • Integrations
    • Community Edition
    • Branching and merging
    • Announcements
  • Plastic SCM 4.0 Beta (Closed)
  • Plastic Cloud
    • General
    • Configuration
  • SemanticMerge
    • General
    • License
    • SCM's configuration
    • Share your experience!
    • External Parsers
  • GitJungle
  • Method History for Subversion

Find results in...

Find results that contain...


Date Created

  • Start

    End


Last Updated

  • Start

    End


Filter by number of...

Joined

  • Start

    End


Group


AIM


MSN


Website URL


ICQ


Yahoo


Jabber


Skype


Location


Interests

Found 3 results

  1. Hi there, I have a branch specific path permission I have applied via the cm acl command which I can see in the GUI, but I am not seeing a way to view this using the showacl command or similar. It only shows the inherited repository permissions. Is there a way to do it? Thanks! Example: User 1 has permissions on path "/" in branch "/main". showacl command does not show User 1. PS C:\Users\ahtrc\wkspaces\tempwk> cm showacl br:/main@reponame1 ACL: 0 User Permission Allowed Denied InheritedFrom User 2 add Yes repserver:servername:serverport User 2 advancedquery Yes repserver:servername:serverport User 2 all Yes repserver:servername:serverport User 2 applyattr Yes repserver:servername:serverport User 2 applylabel Yes repserver:servername:serverport User 2 changecomment Yes repserver:servername:serverport User 2 change Yes repserver:servername:serverport User 2 chgowner Yes repserver:servername:serverport User 2 chgperm Yes repserver:servername:serverport User 2 ci Yes repserver:servername:serverport User 2 configlocks Yes repserver:servername:serverport User 2 mergefrom Yes repserver:servername:serverport User 2 mkattr Yes repserver:servername:serverport User 2 mkchildbranch Yes repserver:servername:serverport User 2 mklabel Yes repserver:servername:serverport User 2 mkrepository Yes repserver:servername:serverport User 2 mktop-levelbranch Yes repserver:servername:serverport User 2 mktrigger Yes repserver:servername:serverport User 2 move Yes repserver:servername:serverport User 2 read Yes repserver:servername:serverport User 2 rename Yes repserver:servername:serverport User 2 replicateread Yes repserver:servername:serverport User 2 replicatewrite Yes repserver:servername:serverport User 2 rmattr Yes repserver:servername:serverport User 2 rmchangeset Yes repserver:servername:serverport User 2 rmlabel Yes repserver:servername:serverport User 2 rmrepository Yes repserver:servername:serverport User 2 rm Yes repserver:servername:serverport User 2 rmtrigger Yes repserver:servername:serverport User 2 view Yes repserver:servername:serverport User 3 add Yes repserver:servername:serverport User 3 advancedquery Yes repserver:servername:serverport User 3 applyattr Yes repserver:servername:serverport User 3 applylabel Yes repserver:servername:serverport User 3 changecomment Yes repserver:servername:serverport User 3 change Yes repserver:servername:serverport User 3 chgowner Yes repserver:servername:serverport User 3 chgperm Yes repserver:servername:serverport User 3 ci Yes repserver:servername:serverport User 3 configlocks Yes repserver:servername:serverport User 3 mergefrom Yes repserver:servername:serverport User 3 mkattr Yes repserver:servername:serverport User 3 mkchildbranch Yes repserver:servername:serverport User 3 mklabel Yes repserver:servername:serverport User 3 mkrepository Yes repserver:servername:serverport User 3 mktop-levelbranch Yes repserver:servername:serverport User 3 mktrigger Yes repserver:servername:serverport User 3 move Yes repserver:servername:serverport User 3 read Yes repserver:servername:serverport User 3 rename Yes repserver:servername:serverport User 3 replicateread Yes repserver:servername:serverport User 3 replicatewrite Yes repserver:servername:serverport User 3 rmattr Yes repserver:servername:serverport User 3 rmchangeset Yes repserver:servername:serverport User 3 rmlabel Yes repserver:servername:serverport User 3 rmrepository Yes repserver:servername:serverport User 3 rm Yes repserver:servername:serverport User 3 rmtrigger Yes repserver:servername:serverport User 3 view Yes repserver:servername:serverport User 4 read Yes repserver:servername:serverport User 4 view Yes repserver:servername:serverport Also tried using other objectspecs with showacl, with no luck: item:C:\Users\ahtrc\wkspaces\tempwk\ item:/@reponame1@servername:serverport path:/@reponame1@servername:serverport path:/ item:/
  2. I'm evaluating Plastic Cloud Edition using Gluon as the front end. I've tried searching the web and forums to see if it is possible to manage access to individual cloud repositories but haven't been able to find any clear information. I'm interested specifically in the following: - Can you grant people access to specific repositories and not others? - Can access be restricted to read-only? - and if so how is this managed?
  3. Hi. I recently started using the path permission feature. Very practical, it allows me to have some private folders in my project that can be un-modifiable or invisible to users or group of users. But working on Unity, asset files come with a meta file. If I fully lock out a user from a folder and don't manually set the same permission for the meta file, the latter will be deleted by their Unity and appears added and deleted in our change set. That means forgetting the meta file would reveal there is a hidden folder to users who should not know about it. This could be solved by adding a multiple paths section feature for starter. And then adding an auto select meta file considering on Unity, it has the exact same name with .meta at the end. Thanks
×
×
  • Create New...