A few Ideas I wanted to suggest...
1. Switching View Type: Would love a way to see our Guru configuration as a non-admin. In other words, toggling to different access level -- i.e. what does my collection look like to someone in X group with Y access level. There are a couple of reasons I would want something like this. First, it allows me when demoing to a new Guru user to show it as they see it. When I demo currently, they're seeing settings and content they'll never have access to. Second, it allows me when building to make sure I have all the right access settings configured. As the main Admin, I see a lot more than they do and I find myself having to triple check that settings are correct.
2. Clone Cards: Creating similar content in different cards (for different user groups) that then have slight tweaks. Would be so much easier to clone the card rather than copy content.
3. Removing Version History: Use case outlined here. Another Guru member just brought up PII concerns too as another reason this would be valuable.
Page 1 / 1
Switching view type is how I demo SFDC successfully to various teams so I definitely support that!
Thanks so much for the suggestions and context on your use cases @heather517 ! For #2, I'm curious if using card templates solves for this?
One more I wanted to add to this in relation to the version history. Part of why I want that is because if I'm collaborating on a card and want another author to view it, I've had to publish for them to see. A 4th ask would be to have a draft setting that is like draft visible to only me or draft visible to me and other authors.
Not quite the same as the request of #2 here but it gave me the idea that it would be cool to have sort of "connected cards" of sorts.
Like a duplicate of Cards that live multiple collections but are only editable within one collection with edits propogating to the other connected Cards. While I know shared boards can help with sharing Cards, something like this would allow for Cards to be contextually included in other collection boards and reduce total number of collections a user sees when browsing to those Cards.
Like a duplicate of Cards that live multiple collections but are only editable within one collection with edits propogating to the other connected Cards. While I know shared boards can help with sharing Cards, something like this would allow for Cards to be contextually included in other collection boards and reduce total number of collections a user sees when browsing to those Cards.
Yes, I love that for cross-team functionality. Where they may not have access to a secondary collection, but the info is relevant for two teams.
The following idea has been merged into this idea:
All the votes have been transferred into this idea.
All the votes have been transferred into this idea.
Enter your E-mail address. We'll send you an e-mail with instructions to reset your password.