Airwatch LLC

Sushilvas Vasavan

Ramani Panchapakesan

Sachin Vas

Saurabh Agrawal

Vijaykumar Bhat

Suja Ramachandran

Pavithra Narayanaswamy

Disclosed are various embodiments for initiating execution of an application using trigger characters. In one embodiment, a computing device detects an entry of a trigger character in an input field of a first user interface presented by a first application. The input field is specified for detection of the individual trigger character based on a trigger rule for the first application. The computing device then identifies a string following the trigger character. The computing device then determines that the string matches a name of a second application installed on the computing device based on a list of applications installed on the computing device. The computing device then initiates execution of the second application. Subsequently, the computing device switches from the first user interface to a second user interface presented by the second application.

Initiating application execution with trigger characters

Disclosed are various examples for multi-party authentication and authentication. In one example, a user can gain access to secured data stored by a managed device based on the presence of the minimum quantity of other users within a threshold proximity of the user who desires access.

Multi-party authentication and authorization

The secure management of attachments is described. In one example, files are identified for attachment to a message through a secure content application extension. Rather than directly attaching the files to the message, a resource locator or link to the files is generated, and the resource locator is inserted into the message. The message is then forwarded for distribution to client devices based on an addressee list for the message. The distribution of and access to the files is managed separately by a management service. The management service can notify the client devices to retrieve the files based on a file access schedule. At each of the client devices, users can access the files through a secure content file application extension using the resource locator during the file access schedule. Thus, the files are distributed through secure content file applications and not as direct attachments to messages.

Secured attachment management

Disclosed are various embodiments for initiating execution of an application using trigger characters. A computing device detects an entry of a trigger character within a first user interface presented by a first application installed on the computing device. The computing device then identifies a string following the trigger character. The computing device then determines that the string matches a name of a second application installed on the computing device. The computing device then initiates execution of the second application. Subsequently, the computing device switches from the first user interface to a second user interface presented by the second application.

Examples of the present disclosure relate to providing policy-protected file access. Some examples involve a configuration profile that includes a credential. The credential permits access to a policy-protected file. Once installed, the configuration profile causes the second credential to be accessible by a file management application of the client device, but inaccessible by a user of the client device. A file management application provides access to the policy-protected file based on the second credential.

Policy protected file access

The secure management of attachments is described. In one example, a message is received by a device management computing environment from a client computing device. The message can include an addressee list, a resource locator to a file, and a schedule associated with an event, for example. The message is intended for distribution to a number of other client devices along with the file according to the addressee list. However, the file is not directly attached to the message. Instead, the distribution of and access to the file is managed separately and securely by the device management computing environment. The device management computing environment can cause the file to be accessible through the client devices using the resource locator based on the schedule associated with the event. Further, after the event, the device management computing environment can cause the file to be inaccessible and/or removed from the client devices.

Examples of the present disclosure relate to protecting files with an information rights policy. Files can be protected as specified by a content policy associated with the file. The content policy can specify whether the file should be protected while at rest on a device as well as when the file is shared with another user of an enterprise.

Applying rights management policies to protected files

Disclosed are various examples for multi-party authentication and authentication. In one example, a user who forgets a password can gain access to secured data stored by a managed device by way of an authorization by one or more other users. This access can be granted even if the managed device is in an off-line mode or if a management server cannot be reached. In another example, access to secured data can depend upon authorization by a minimum quantity of other users. The authorization can involve an explicit approval or disapproval. Alternatively, the authorization can correspond to the presence of the minimum quantity of other users within a threshold proximity of the user who desires access.

Growing community of inventors

Bengaluru, India

Sushilvas Vasavan