Abstract: Disclosed are various approaches for providing touchless visitor management. A visitor can complete a visitor registration process using a client device of the visitor and obtain a virtual badge credential to a visitor's device. A physical access control system credential as well as a visitor badge can also be obtained to the visitor's device.

Abstract: Methods and systems are described for analyzing and attesting physical access to a location. In an example, an administrator can create a survey for users in an organization. The survey can be sent to a user device as a notification. The user can complete the survey, and the user's physical access rights can be determined based on the survey answers. When the user attempts to gain access to a location of the organization, the user can provide a digital access badge. The digital access badge can be mapped to the user's access permissions. The user can be granted or denied access depending on whether the user answered the survey and, if answered, what answers the user provided.

Abstract: Systems and methods are described for content sharing in an enterprise digital space. A graphical user interface (“GUI”) can include a feature that allows users to save bookmarks in a single location. A user can request to create a bookmark, and a bookmark service can verify that the bookmark satisfies enterprise security policies. The bookmark service can also verify that the bookmark does not violate any access policies associated with the requesting user. The GUI can provide a feature that allows users to share saved bookmarks with other users in the enterprise by searching for individual users or groups. When a user requests to share a bookmark, the bookmark service can verify that the bookmark does not violate any access policies of the intended recipient. To share the bookmark, the bookmark service can utilize a notification service to send a notification to the recipient's user device.

Abstract: A notification builder implemented through a graphical user interface (“GUI”) provides a platform for building notifications and defining priorities for how the notifications will be presented to users of managed devices. Elements included in the notification builder and selectable as part of a build process can provide options for naming a notification, providing content for the notification, defining recipients, setting a respective priority, and creating action buttons. An action button can allow a user that has received a notification built with the notification builder to interact with the notification in a predetermined manner. The GUI can also provide data relating to the notification, such as success/failure, read/unread, etc.

Abstract: Disclosed are various approaches for providing touchless visitor management. A visitor can complete a visitor registration process using a client device of the visitor and obtain a virtual badge credential to a visitor's device. A physical access control system credential as well as a visitor badge can also be obtained to the visitor's device.

Abstract: Methods and systems are described for analyzing and attesting physical access to a location. In an example, an administrator can create a survey for users in an organization. The survey can be sent to a user device as a notification. The user can complete the survey, and the user's physical access rights can be determined based on the survey answers. When the user attempts to gain access to a location of the organization, the user can provide a digital access badge. The digital access badge can be mapped to the user's access permissions. The user can be granted or denied access depending on whether the user answered the survey and, if answered, what answers the user provided.

Abstract: A notification builder implemented through a graphical user interface (“GUI”) provides a platform for building notifications and defining priorities for how the notifications will be presented to users of managed devices. Elements included in the notification builder and selectable as part of a build process can provide options for naming a notification, providing content for the notification, defining recipients, setting a respective priority, and creating action buttons. An action button can allow a user that has received a notification built with the notification builder to interact with the notification in a predetermined manner. The GUI can also provide data relating to the notification, such as success/failure, read/unread, etc.

Abstract: Disclosed are various approaches for providing touchless visitor management. A visitor can complete a visitor registration process using a client device of the visitor and obtain a virtual badge credential to a visitor's device. A physical access control system credential as well as a visitor badge can also be obtained to the visitor's device.

Abstract: A notification builder implemented through a graphical user interface (“GUI”) provides a platform for building notifications and defining priorities for how the notifications will be presented to users of managed devices. Elements included in the notification builder and selectable as part of a build process can provide options for naming a notification, providing content for the notification, defining recipients, setting a respective priority, and creating action buttons. An action button can allow a user that has received a notification built with the notification builder to interact with the notification in a predetermined manner. The GUI can also provide data relating to the notification, such as success/failure, read/unread, etc.

Abstract: A notification builder implemented through a graphical user interface (“GUI”) provides a platform for building notifications and defining priorities for how the notifications will be presented to users of managed devices. Elements included in the notification builder and selectable as part of a build process can provide options for naming a notification, providing content for the notification, defining recipients, setting a respective priority, and creating action buttons. An action button can allow a user that has received a notification built with the notification builder to interact with the notification in a predetermined manner. The GUI can also provide data relating to the notification, such as success/failure, read/unread, etc.

Abstract: A notification builder implemented through a graphical user interface (“GUI”) provides a platform for building notifications and defining priorities for how the notifications will be presented to users of managed devices. Elements included in the notification builder and selectable as part of a build process can provide options for naming a notification, providing content for the notification, defining recipients, setting a respective priority, and creating action buttons. An action button can allow a user that has received a notification built with the notification builder to interact with the notification in a predetermined manner. The GUI can also provide data relating to the notification, such as success/failure, read/unread, etc.

Abstract: A notification builder implemented through a graphical user interface (“GUI”) provides a platform for building notifications and defining priorities for how the notifications will be presented to users of managed devices. Elements included in the notification builder and selectable as part of a build process can provide options for naming a notification, providing content for the notification, defining recipients, setting a respective priority, and creating action buttons. An action button can allow a user that has received a notification built with the notification builder to interact with the notification in a predetermined manner. The GUI can also provide data relating to the notification, such as success/failure, read/unread, etc.

Abstract: A method and system for implementing data retention policies on data stored within distributed file systems. Embodiments of the technology enable a content object retention management controller to apply a data retention policy on sets of content objects stored on a distributed file system via a single proxy object. In one or more embodiments of the technology, the request to apply the data retention policy on the single proxy object ultimately propagates the application of the data retention policy to the set of associated content objects (and, as appropriate, directories) stored in the distributed file system. In one or more embodiments of the technology, a content object may be a file (or any portion thereof) and/or a directory (or any portion thereof).