Abstract: A data processing system implements detecting that a first user device associated with a first user has added a first sponsored content item to a host electronic document by adding a first reference to the first sponsored content item to the host electronic document. The first sponsored content item is stored separately in a memory of a cloud-based service from the host electronic document. The data processing system further implements determining that the first user has permission to share the first sponsored content item with other users of the cloud-based service, generating sponsor information to associate the sponsored content item with the host electronic document to permit users having access to the host electronic document to access the sponsored content item, and storing the sponsor information in a sponsored access datastore.

Abstract: A computing system includes a processor and memory storing instructions executable by the at least one processor. The instructions, when executed, provide a user interface component that receives an indication of an external user with which to share an item of electronic content, a link generation component that generates a link to share the item of electronic content and identifies a communication endpoint associated with the external user, and an access control component that receives a request to access the item of electronic content using the link and, in response to the request, generates an access code that is communicated to the communication endpoint associated with the external user. The user interface component receives an access input, and the access control component grants access to the item of electronic content based on a determination that the access input includes the access code communicated to the communication endpoint associated with the external user.

Abstract: In one embodiment, a network file management system 120 may use a persistent metadata store 410 and an access control list 420 to facilitate a batch rollout. The network file management system 120 may maintain a content database 312. A network file management system 120 may store a metadata set for the content database 312 in a separate persistent metadata store 410.

Abstract: A computing system includes a processor and a data store coupled to the processor. The computing system is configured to provide access to electronic content stored in the data store. A user interface component is configured to receive an indication of an external user with which to share an item of electronic content. A link generation component is configured to generate a link to share the item of electronic content. An access control component is configured to receive a request to access the item of electronic content using the link, and responsively generate an access code that is communicated to a known endpoint associated with the link. The user interface component is configured to receive a user input containing a user-entered access input. The access control component is configured to selectively grant access to the item of electronic content based on whether the user-entered access input matched the access code communicated to the known endpoint associated with the link.

Abstract: In one embodiment, a network file management system 120 may use a persistent metadata store 410 and an access control list 420 to facilitate a batch rollout. The network file management system 120 may maintain a content database 312. A network file management system 120 may store a metadata set for the content database 312 in a separate persistent metadata store 410.

Abstract: Architecture that enables separation of a user interface (UI) upgrade from the content and application logic upgrade. Administrators can upgrade to take advantage of new infrastructure features, and independently schedule the UI upgrade, for example, to accommodate customization work or to ensure user training. Furthermore, administrators can now allow users to choose when to switch to the new UI. More specifically, the architecture facilitates the separation of a UI upgrade from content and application logic upgrade, the ability to control the UI upgrade at multiple levels of precision, the ability for application logic and UI components to change behaviors based on the UI version of the context, and the ability to “preview” the updated UI before permanently switching to it. Additionally, UI components can be filtered to only appear in the appropriate UI version, and the site's UI version can be compared to versions that a component is compatible with.

Abstract: Upgrade control checks may be provided. A user may be notified that at least one upgrade is available. In response to receiving a selection of the at least one upgrade from the user, a check may be made to determine whether the at least one upgrade conflicts with an existing component. If no conflict is detected, the upgrade may be performed. If a conflict does exist, a repair may be attempted.

Abstract: Architecture that enables separation of a user interface (UI) upgrade from the content and application logic upgrade. Administrators can upgrade to take advantage of new infrastructure features, and independently schedule the UI upgrade, for example, to accommodate customization work or to ensure user training. Furthermore, administrators can now allow users to choose when to switch to the new UI. More specifically, the architecture facilitates the separation of a UI upgrade from content and application logic upgrade, the ability to control the UI upgrade at multiple levels of precision, the ability for application logic and UI components to change behaviors based on the UI version of the context, and the ability to “preview” the updated UI before permanently switching to it. Additionally, UI components can be filtered to only appear in the appropriate UI version, and the site's UI version can be compared to versions that a component is compatible with.

Abstract: Technologies are described herein for generating and changing credentials of a service account. In one method, a credential schedule is retrieved. The credential schedule specifies when a plurality of credentials are scheduled to be changed. A determination is made whether a current credential associated with the service account is scheduled to be changed according to the credential schedule. Upon determining that the current credential is scheduled to be changed, at least part of a new credential is generated. The current credential is replaced with the new credential for the service account.

Abstract: Technologies are described herein for generating and changing credentials of a service account. In one method, a credential schedule is retrieved. The credential schedule specifies when a plurality of credentials are scheduled to be changed. A determination is made whether a current credential associated with the service account is scheduled to be changed according to the credential schedule. Upon determining that the current credential is scheduled to be changed, at least part of a new credential is generated. The current credential is replaced with the new credential for the service account.