Abstract:
A content management system implementing methodologies providing retroactive shared content item links is disclosed. The content management system and methodologies allow a team administrator of a team to configure a team-wide shared link policy that determines whether non-team members can access content items associated with team accounts using shared links generated for the content items by team members. The team shared link policy has two settings. In a first setting, the content management system allows non-team members to use shared links generated by team members to access content items associated with team accounts. In a second setting, the content management system blocks access to the content items by non-team members. Shared links are retroactive in the sense they do not need to be regenerated after the team shared link policy has been changed from the second setting back to the first setting.
Abstract:
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.
Abstract:
Techniques are described herein for managing unsynchronized content items when the personal computing devices storing the unsynchronized content items are unlinked from a content item synchronization service. The techniques involve treating synchronized content items differently from unsynchronized content items. For example, after a personal computing is unlinked from the service, synchronized content items may be removed or deleted from the personal computing device and unsynchronized content items encrypted and/or moved to another data storage location.
Abstract:
A content management system implementing methodologies providing retroactive shared content item links is disclosed. The content management system and methodologies allow a team administrator of a team to configure a team-wide shared link policy that determines whether non-team members can access content items associated with team accounts using shared links generated for the content items by team members. The team shared link policy has two settings. In a first setting, the content management system allows non-team members to use shared links generated by team members to access content items associated with team accounts. In a second setting, the content management system blocks access to the content items by non-team members. Shared links are retroactive in the sense they do not need to be regenerated after the team shared link policy has been changed from the second setting back to the first setting.
Abstract:
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.
Abstract:
Nested namespaces for selective content sharing. In one embodiment, for example, a computer-implemented method includes the steps of: receiving a request to share a content item with a first set of user accounts held with a content management system; determining a first namespace to which the content item belongs; based on detecting that a second set of user accounts allowed to access the first namespace is different from the first set of user accounts, creating a second namespace nested in the first namespace; associating the first set of user accounts with the second namespace; and based on the first set of user accounts being associated with the second namespace, allowing the first set of user accounts to access content items, including the content item, belonging to the second namespace.
Abstract:
Systems, methods, and non-transitory computer-readable storage media for serving content stored in an online synchronized content management system from a sandbox domain via a temporary address. The online synchronized content management system may receive a first request from a user to access a content item stored in the system. The first request may be received at a first domain via a first address that is directed to the first domain. The system may generate a second address that is directed to a second domain such as a sandbox domain. Then, the second address can be associated with the content item for direct access. When the system receives, at the second domain via the second address, a second request to access the content item, the content item can be served from the second domain. After the system receives the second request, it can generate and issue a session identifier for the second address to verify any subsequent requests to access the content item via the second address.
Abstract:
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.