Content item sharing and synchronization system with team shared folders
View Patent ↗A content item sharing and synchronization system providing team shared folders is described. Users of the system have access to the team shared folder simply by being a member of a team. A team account manager of the team can grant access to the team shared folder simply by inviting selected users to the team. Similarly, the team account manager can revoke access to the team shared folder simply by removing a user from the team. Unlike typical network file server folders, separate access control list management for the team shared folder apart from user team membership management is not needed to grant and revoke access to the team shared folder, thereby reducing administrative steps necessary to effectively manage access to the team shared folder.
1. A method comprising:
receiving an indication that a first user accepted an invitation to join a team;
wherein a second user is already a member of the team when the indication is received;
wherein the second user is not the first user;
in response to receiving the indication that the first user accepted the invitation to join the team, performing team joining operations comprising (a), (b) and (c);
wherein the team joining operation (a) comprises joining the first user to the team of which the second user is already a member;
wherein the team joining operation (b) comprises determining whether a team shared folder of the team is active or inactive as configured by the second user;
wherein determining whether a team shared folder of the team is active or inactive comprises examining metadata associated with the team shared folder that specifies whether the team shared folder is active or inactive;
wherein the team joining operation (a) comprises joining the first user to the team irrespective of whether the team shared folder is active or inactive; and
wherein the team joining operation (c) comprises automatically causing, based on a first copy of the team shared folder stored at one or more server computing devices, a separate second copy of the team shared folder to be stored at a client computing device of the first user, only if the metadata associated with the team shared folder specifies that the team shared folder is active;
wherein the method is performed by one or more computing devices.
2. The method of claim 1 , further comprising:
in response to receiving the indication that the first user accepted the invitation to join the team, adding the first user to the team;
receiving a request from the second user that is not the first user to remove the first user from the team; and
in response to receiving the request to remove the first user from the team, causing the second copy of the team shared folder to be removed from the client computing device of the first user.
3. The method of claim 1 , further comprising:
sending the invitation to the first user to join the team comprises by sending an e-mail message to the first user.
4. The method of claim 1 , wherein receiving the indication that the first user accepted the invitation to join the team comprises receiving the indication from the client computing device of the first user.
5. The method of claim 1 , further comprising:
receiving a request from the second user that is not the first user to deactivate the team shared folder; and
in response to receiving the request to deactivate the team shared folder, causing the second copy of the team shared folder to be removed from the client computing device of the first user.
6. The method of claim 1 , wherein causing the second copy of the team shared folder to be stored at the client computing device of the first user comprises synchronizing (a) a client repository stored at the client computing device that initially does not contain the second copy of the team shared folder with (b) a server repository stored at the one or more server computing devices that contains the first copy of the team shared folder.
7. The method of claim 1 , wherein the first copy of the team shared folder contains one or more content items; and wherein causing the second copy of the team shared folder to be stored at the client computing device of the first user comprises causing copies of the one or more content items to be stored in the second copy of the team shared folder at the client computing device of the first user.
8. The method of claim 1 , further comprising:
sending the invitation to the first user to join the team;
prior to sending the invitation to the first user to join the team, receiving a request from the second user that is not the first user to send the invitation to the first user to join the team.
9. The method of claim 3 , further comprising:
sending the invitation to the first user to join the team;
prior to sending the invitation to the first user to join the team, receiving a request from the second user that is not the first user to create the team; and in response to receiving the request from the second user to create the team, creating the team with the second user initially as the only member of the team.
10. The method of claim 1 , further comprising:
in response to receiving the indication that the first user accepted the invitation to join the team, adding the first user to the team.
11. A system comprising:
one or more processors;
one or more non-transitory computer-readable media storing instructions to be executed by the one or more processors, the instructions configured for:
receiving an indication that a first user accepted an invitation to join a team;
wherein a second user is already a member of the team when the indication is received;
wherein the second user is not the first user;
in response to receiving the indication that the first user accepted the invitation to join the team, performing team joining operations comprising (a), (b) and (c);
wherein the team joining operation (a) comprises joining the first user to the team of which the second user is already a member;
wherein the team joining operation (b) comprises determining whether a team shared folder of the team is active or inactive as configured by the second user;
wherein determining whether a team shared folder of the team is active or inactive comprises examining metadata associated with the team shared folder that specifies whether the team shared folder is active or inactive;
wherein the team joining operation (a) comprises joining the first user to the team irrespective of whether the team shared folder is active or inactive; and
wherein the team joining operation (c) comprises automatically causing, based on a first copy of the team shared folder stored at one or more server computing devices, a separate second copy of the team shared folder to be stored at a client computing device of the first user, only if the metadata associated with the team shared folder specifies that the team shared folder is active.
12. The system of claim 11 , the instructions further configured for:
in response to receiving the indication that the first user accepted the invitation to join the team, adding the first user to the team;
receiving a request from the second user that is not the first user to remove the first user from the team; and
in response to receiving the request to remove the first user from the team, causing the second copy of the team shared folder to be removed from the client computing device of the first user.
13. The system of claim 11 , the instructions further configured for sending the invitation to the first user to join the team by sending an e-mail message to the first user.
14. The system of claim 11 , the instructions further configured for receiving the indication that the first user accepted the invitation to join the team comprises receiving the indication from the client computing device of the first user.
15. The system of claim 11 , the instructions further configured for:
receiving a request from the second user that is not the first user to deactivate the team shared folder; and
in response to receiving the request to deactivate the team shared folder, causing the second copy of the team shared folder to be removed from the client computing device of the first user.
16. The system of claim 11 , wherein the instructions configured for causing the second copy of the team shared folder to be stored at the client computing device of the first user comprise instructions configured for synchronizing (a) a client repository stored at the client computing device that initially does not contain the second copy of the team shared folder with (b) a server repository stored at the one or more server computing devices that contains the first copy of the team shared folder.
17. The system of claim 11 , wherein the first copy of the team shared folder contains one or more content items; and wherein the instructions configured for causing the second copy of the team shared folder to be stored at the client computing device of the first user comprise instructions configured for causing copies of the one or more content items to be stored in the second copy of the team shared folder at the client computing device of the first user.
18. The system of claim 11 , the instructions further configured for:
sending the invitation to the first user to join the team; and
prior to sending the invitation to the first user to join the team, receiving a request from the second user that is not the first user to send the invitation to the first user to join the team.
19. The system of claim 11 , the instructions further configured for:
sending the invitation to the first user to join the team; and
prior to sending the invitation to the first user to join the team, receiving a request from the second user that is not the first user to create the team; and in response to receiving the request from the second user to create the team, creating the team with the second user initially as the only member of the team.
20. The system of claim 11 , the instructions further configured for:
in response to receiving the indication that the first user accepted the invitation to join the team, adding the first user to the team.