Shared Access- groups

Thanks for sharing this idea with us, ​@AScott . We’ve reviewed it and appreciate the thought behind it.

At this time, we’re not planning to pursue this request, so we’ve marked it as parked. 

While it’s not on our current roadmap, ideas like yours help inform future direction if priorities change.

Thanks again for contributing your input.

​@Raileen.Del Hello, thanks for responding.   Is there anything we can do make this happen?  This is a very time consuming issue for us.

​@AScott I surfaced the urgency to the product team! Hopefully, we will have an update for you soon.

In the meantime, I wanted to point you to the Accounts:updateSharedAccess endpoint. You can bulk provision users by including a list of user IDs in the request body. Maybe this workaround will be helpful in the interim :) 

We have this same issue. we are using Custody Transfer for a Team (Group) to send envelops from a common email address and collate all the envelops in a single place. But we need each team member to login with their own credentials so don’t want them to login into this shared account. 

Therefore, we have an issue, if a team member is away or leaves, then others in the team cannot address any issues with envelopes sent by them.

Our hope was that shared access would resolve this, i.e. if each team member shares a folder with the team Group. But sharing with a Group is not supported, which means its the responsibility of each team member to share with all the other team members. This is never going to happen and when you factor leavers and new starters in the team its demonstrates how poor the current shared access feature is. it just does not scale when you have a team processing many envelopes

We need to be able to share with groups and we need the group membership to sync to our Directory so it automatically updates with leavers and new starters, without this continuing to use Docusign may not be feasible

Therefore, please reconsider the decision to park this request

Hi ​@ididwhat, thank you for your feedback. I’ll send this thread over to the product team to convey the demand for this feature. 

Have you tried the workaround I mentioned in my earlier reply? Let me know if you get a chance to try it :)