Ability to Make Global Segments Not Editable

Comments

6 comments

  • Sean Maguire

    Danielle's use case above seems to be: User1 creates a Global segment and marks it as Public, but then is also granted a new option to classify it as read-only. Visible to other users, still available to those other users for making copies / clones, just not editable directly... They can use it and borrow it, but not make changes or overwrite the original. It's Public, and read-only.

    That would be a great start, but would also be great having the ability to have a subset of Totango users who CAN edit the source segment in partnership with the owner.

    For example: User1 creates a Public and Read-Only segment, but wants to grant edit permission to other members of their team. User1 should have the option to "share" ownership with other collaborators like User2, User3, and User4... each of whom can all edit it just like User1 can, and all while other Totango users (UserX...UserX+N) cannot do that and see it as Read-only.

    Those types of granular permission options would be a big help for Global segments.

    Less useful, but still would help: The ability to mark a segment as Private but still be able to share it with a subset of chosen users. Essentially, in addition to the current settings of Private and Public for global segments, offer a new type such as "Somewhat Private." The segment would be "Private to Group" versus today's only options of  "Private to Individual" or "Public to Everyone."

    Thanks for your consideration. The ability to have a Public, but Read-Only segment in Global as Danielle requested would be a nice start if the other suggestions I've added here prove to be more technically complex to deliver

    1
    Comment actions Permalink
  • Danielle Young

    I second all of the items listed from Sean! 

    0
    Comment actions Permalink
  • Cindy Wang

    I am having issues with not knowing someone were editing segments that I feed into scorecards; and the scorecards are all wrong. It would be good to have a lock-down segment ability that prevents this situation.

    1
    Comment actions Permalink
  • Vijay

    Cindy / Danielle and Sean,

    If the segments live in a SuccessBLOC and are in a published state, all the segments within it can only be changed by a Global Admin creator, collaborator or team admin. 

    Does that option not work? 

    Thanks

    Vijay

    0
    Comment actions Permalink
  • Sean Maguire

    Vijay - I believe there may be a relevant distinction to be here between standard SuccessBlocs and the Global SuccessBloc. This request seems specific to Global. 

    For us, the permissions work fine in our standard blocs (like Onboarding, for example), however every one of our Totango users is permissioned to Global so they may create their own. Consequently, we have literally thousands of people who have the ability to edit/delete things created and managed by others... things they shouldn't be able to edit or delete (even though they're Publicly shared).

    I'll defer to Danielle and Cindy if perhaps my feedback here is in error or if maybe they have a different experience. Likewise, if there's a setting you know of that allows us to better manage this permissions issue already, I'd be curious to learn more. Thanks. 

    0
    Comment actions Permalink
  • Laurence Dean (Group)

    Team,

    I need to be able as an admin to control the blocks, but as Sean mentions it would be good to have others that can contribute to the segment. My challenge, which is why i feel this is a Global not a SuccessBloc one is that i need this for both Spark and Zoe based users, and Zoe based user dont have access to SuccessBloc's.

    0
    Comment actions Permalink

Please sign in to leave a comment.