Improve management of pending invitations via API
As we continue to build and customize the collaboration mechanism we found it difficult to manage pending invitations. When calling your API api.box.com/2.0/folders<folderid>/collaborations it returns approved collaborators in the “accessibleby” object but when it return PENDING collaborators the “accessible_by” object is null, but there’s status “pending” on this collaborator. We would imagine it would capture the email address of that pending collaborator. Seeing this is capable in your public domain to show the pending collaborator with an email address would be very useful to create modules to manage pending collaborators (e.g. resending the invitation, update the email address, etc..).
The temporary solution that was offered:
1) create our own database to manage and capture external emails that were sent invitation to collaborate
2) query the event logs to find those external emails.
It doesn’t seem to be very efficient for us to adopt these solutions for the interim when BOX’s API already aware of the email value and Box has the mechanism to manage these pending collaborators and move them to approved once they have a profile in Box.com. This will also help reduce traffic and processes if Box can capture this detail in the collaboration dataset.
I vote for this idea in that it is very similar to what we want but it would be great to also have a way to manage pending invitations from the administration console.
Currently there are Pending Invitations in our tenant. Is there a way to remove a pending user, without having to traverse each folder?
There is a user from our legacy content management system which is the API user, who is collaborated into each room (as an admin in order to download the room content from the legacy system.
That user is "Pending" in many folders, it would be great to remove that user from ALL pending collaborations.