Automatic application installation and integration at an enterprise level based on a single install request
Abstract
The present disclosure relates to systems, methods, and non-transitory computer readable media for automatically providing access to multiple user accounts associated with an enterprise account based on a single install request. In so doing, the disclosed systems can rapidly and automatically integrate a developer system with the enterprise account. For example, the disclosed systems can, for a requested application created by a developer system, determine application ID and authentication credential pairs unique to each user account that enable secure, independent access to the requested application for each user account. In addition, the disclosed systems can provide such access to the requested application on user devices through the associated user accounts without users having to separately login to the requested application. Further, the disclosed systems can handle access changes on an individual user account basis while maintaining cross-system synchronization.
Claims
exact text as granted — not AI-modifiedWhat is claimed is:
1 . A method comprising:
receiving a request for access change to a user account from a user device by an enterprise system; provide a notification of the request to a developer system by the enterprise system; receiving a decision with respect to the request by the enterprise system from the developer system, wherein the decision is received before the expiration of a threshold sync time; and relaying the decision to the user device by the enterprise system.
2 . The method of claim 1 , further comprising:
determining that no decision has been received from the developer system after the expiration of the threshold sync time; and in response to the determining, enabling direct contact between the user device and the developer system.
3 . The method of claim 2 , wherein enabling direct contact between the user device and the developer system comprises informing the user device of a direct connection to contact the developer system.
4 . The method of claim 1 , further comprising:
determining that no decision has been received from the developer system after the expiration of the threshold sync time; and in response to the determining, canceling the request for access change.
5 . The method of claim 1 , further comprising:
determining that no decision has been received from the developer system after the expiration of the threshold sync time; and in response to the determining:
accepting the request for access change on behalf of the developer system; and
updating the developer system to reflect the access change.
6 . The method of claim 1 , wherein the request for access change is a request to remove access to an application for the user account.
7 . A system comprising:
at least one processor; and at least one non-transitory computer-readable storage medium storing instructions that, when executed by the at least one processor, cause the system to:
receive a request for access change to a user account from a user device;
provide a notification of the request to a developer system;
receive a decision with respect to the request from the developer system, wherein the decision is received before the expiration of a threshold sync time; and
relay the decision to the user device.
8 . The system of claim 7 , further comprising instructions that, when executed by the at least one processor, cause the computer system to:
determining that no decision has been received from the developer system after the expiration of the threshold sync time; and in response to the determining, enabling direct contact between the user device and the developer system.
9 . The system of claim 8 , wherein enabling direct contact between the user device and the developer system comprises informing the user device of a direct connection to contact the developer system.
10 . The system of claim 7 , further comprising instructions that, when executed by the at least one processor, cause the system to:
determining that no decision has been received from the developer system after the expiration of the threshold sync time; and in response to the determining, canceling the request for access change.
11 . The system of claim 7 , further comprising instructions that, when executed by the at least one processor, cause the system to:
determining that no decision has been received from the developer system after the expiration of the threshold sync time; and in response to the determining:
accepting the request for access change on behalf of the developer system; and
updating the developer system to reflect the access change.
12 . The system of claim 7 , wherein the system is an enterprise system.
13 . The systm of claim 7 , wherein the request for access change is a request to remove access to an application for the user account.
14 . A non-transitory computer-readable medium storing instructions that, when executed by at least one processor, cause a computer system to:
receive a request for access change to a user account from a user device; provide a notification of the request to a developer system; receive a decision with respect to the request from the developer system, wherein the decision is received before the expiration of a threshold sync time; and relay the decision to the user device.
15 . The computer-readable medium of claim 14 , further comprising instructions that, when executed by the at least one processor, cause the computer system to:
determining that no decision has been received from the developer system after the expiration of the threshold sync time; and in response to the determining, enabling direct contact between the user device and the developer system.
16 . The computer-readable medium of claim 15 , wherein enabling direct contact between the user device and the developer system comprises informing the user device of a direct connection to contact the developer system.
17 . The computer-readable medium of claim 14 , further comprising instructions that, when executed by the at least one processor, cause the system to:
determining that no decision has been received from the developer system after the expiration of the threshold sync time; and in response to the determining, canceling the request for access change.
18 . The computer-readable medium of claim 14 , further comprising instructions that, when executed by the at least one processor, cause the system to:
determining that no decision has been received from the developer system after the expiration of the threshold sync time; and in response to the determining:
accepting the request for access change on behalf of the developer system; and
updating the developer system to reflect the access change.
19 . The computer-readable medium of claim 14 , wherein the system is an enterprise system.
20 . The computer-readable medium of claim 14 , wherein the request for access change is a request to remove access to an application for the user account.Join the waitlist — get patent alerts
Track US2020371766A1 — get alerts on status changes and closely related new filings.
We store only your email — no account needed. See our privacy policy.