Sean Bronee
My feedback
12 results found
-
28 votesSean Bronee supported this idea ·
-
8 votesSean Bronee supported this idea ·
-
84 votes
Because of the downstream impacts, we will not be solving this problem as requested. We will be looking at a more holistic approach to prevent unintended consequences of file operations.
Sean Bronee supported this idea · -
15 votesSean Bronee supported this idea ·
-
5 votesSean Bronee supported this idea ·
-
Collaborators Page (Item-Level) -- Add Ability to Sort by Column Headers / Filter by External Collab
58 votesDue to other higher priority items, we are not planning on this at this time.
Sean Bronee supported this idea · -
2 votesSean Bronee supported this idea ·
-
3 votesSean Bronee supported this idea ·
-
13 votes
An error occurred while saving the comment Sean Bronee supported this idea · -
9 votesSean Bronee supported this idea ·
-
22 votes
Not currently planned at this time.
Sean Bronee supported this idea · -
4 votes
As access and user maintenance are the most critical aspects of our configuration, it would make most sense to us to allow users to be replicated (i.e. not dummy), in sand and prod, so that changes to the configuration can be tested with end-users using real-life access scenarios (such as logging with SSO, or logging in as external), or being parts of groups that are synced with the AD. Note that we don't need all users replicated (especially not externals) necessarily, but need to be able to invite some users on both environments so they can login in a similar way on both environments using their real email and credentials