Anonymous
My feedback
14 results found
-
25 votesAnonymous
supported this idea
·
-
26 votesAnonymous
supported this idea
·
-
27 votesAnonymous
supported this idea
·
-
30 votesAnonymous
supported this idea
·
-
29 votesAnonymous
supported this idea
·
-
38 votesAnonymous
supported this idea
·
-
82 votesAnonymous
supported this idea
·
-
123 votesAnonymous
supported this idea
·
-
1 voteAnonymous
shared this idea
·
-
5 votes
We have made the text for long folder names wrap in the Edit Shared Folders view, so cut off folder names with a company or department prefix should no longer be a problem.
However, we have not made the folders name column on the page sortable and don’t currently have plans to make this sortable.
Anonymous
supported this idea
·
-
8 votes
This does sound like a huge burden for admins and I’d like to hear more about how you’d use existing AD groups to grant co-admin permissions. We are looking into extending our APIs to allow admins to set co-admin permissions, which may alleviate the pain of setting the permissions manually.
However, we don’t currently have any plans to take the AD groups and map them to co-admin permissions at this time.
An error occurred while saving the comment Anonymous
supported this idea
·
-
3 votes
An error occurred while saving the comment Anonymous
commented
Same for all groups provisioned via SCIM.
We push groups from okta to box.com; they shouldn't be editable in box.com !!
That's obvious!Anonymous
supported this idea
·
-
30 votes
At this time, we are developing solutions for using groups to grant access to apps and enterprise settings. https://pulse.box.com/forums/909778/suggestions/36670615
Supporting nested groups may be a longer term vision that we consider after solving the first problem above.
Anonymous
supported this idea
·
-
65 votes
Interesting idea, but unlikely to be prioritized this year.
Anonymous
supported this idea
·
Same for all groups provisioned via SCIM, it would be great to map groups that comes from iDP to admin roles in box.com