Abstract:
Techniques for invite enforcement. In one embodiment, for example, a method comprises: receiving an acceptance of an invitation to join a team of one or more team user accounts held with the online service; based on receiving the acceptance and based on determining that an owned domain name service domain of an owned electronic mail address is associated with the team, offering a personal user account an option between at least: (a) converting the personal user account to a team user account that is a member of the team, and (b) changing an electronic mail address associated with the personal user account from the owned electronic mail address to one that has a different domain name service domain than the owned domain name service domain associated with the team.
Abstract:
In one embodiment, for example, a method comprises: receiving an acceptance of an invitation to join a team of one or more team user accounts held with the online service; based on receiving the acceptance and based on determining that an owned domain name service domain of an owned electronic mail address is associated with the team, offering a personal user account an option between at least: (a) converting the personal user account to a team user account that is a member of the team, and (b) changing an electronic mail address associated with the personal user account from the owned electronic mail address to one that has a different domain name service domain than the owned domain name service domain associated with the team.
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:
Techniques for invite enforcement and domain capture. In one embodiment, for example, a method performed in an online service computing environment comprises the operations of: storing, in a database, an association between a team of one or more user accounts and a domain name service domain; receiving a request to invite an e-mail address belonging to the domain name service domain to join the team; creating, in a database, a placeholder user account that is a member of the team; associating, in a database, the e-mail address with the placeholder user account; and after an invitation for the e-mail address to join the team is accepted, converting, in a database, the individual user account to a team account that is (a) a member of the team and (b) associated with the e-mail address.
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:
Various embodiments of the disclosed technology can obtain information about associations between users (e.g., user accounts) of a content management system and applications compatible with the content management system. Various embodiments can also obtain information about a plurality of attributes associated with usage of the content management system by the users (e.g., user accounts). In some embodiments, the attributes can include a device property, a usage pattern, an account property, a content item property, a profile property, a preference property, or a domain property. Moreover, data about social connections of the users (e.g., user accounts) can also be obtained. Based, at least in part, on at least one of the information about the associations, the information about the plurality of attributes, or the data about the social connections, one or more applications can be recommended to a selected user (e.g., a selected user account).
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.