IP Library Granted Patent US 11,863,640
Granted Patent B2
US 11,863,640 · App. 17/953,147 · Granted Jan 2, 2024

System, method, and apparatus for generating a third-party resource usage map in a group based communication system

Inventors: Meagan Gamache (San Francisco, CA); Buster Benson (San Francisco, CA)
Assignee: Salesforce, Inc.
H04L67/53H04L63/0807H04L67/535H04L63/10
View Patent ↗
Loading inventors, assignments & file history…
Monitor This Case
Get email alerts when status or documents change.
Order Certified Copies
Most orders are placed with the USPTO same day — all within 24 business hours.
Order via The Patent Place →
Pre-filled with this patent's details
Quick Facts
Patent No.
US 11,863,640
App. No.
17/953,147
Granted
Jan 2, 2024
Kind
B2
Abstract

Embodiments of the present disclosure provide methods, systems, apparatuses, and computer program products for generating a third-party resource usage map in a group based communication system, where the third-party resource usage map comprises a plurality of third party resource usage records and each third-party resource usage record comprises a user identifier, a third-party resource provider identifier, and a third-party resource access token.

Claims (50)

1. A method, implemented at least in part by a server computing device associated with a group-based communication platform, comprising:

receiving, from a first third-party resource provider, a first third-party resource access token;

receiving, from a first client device associated with a first user, a first third-party resource access request, the first third-party resource access request comprising a first user identifier and a first third-party resource provider identifier;

retrieving, based at least in part on receiving the first third-party resource access request and from a group-based communication repository maintained by the group-based communication platform, a plurality of third-party resource usage records, wherein individual ones of the plurality of third-party resource usage records are associated with a different user identifier,

determining that a second third-party resource provider identifier associated with a second third-party resource provider is absent from the plurality of third-party resource usage records; and

transmitting, to respective client devices associated with the individual ones of the plurality of third-party resource usage records, a recommendation to access a second third-party resource, wherein the recommendation to access the second third-party resource comprises the second third-party resource provider identifier.

2. The method of claim 1 , wherein the recommendation to access the second third-party resource is configured to be rendered for display on individual ones of the respective client devices.

3. The method of claim 1 , further comprising:

receiving, from a second client device of the respective client devices and in response to a recommendation to access the second third-party resource, a second third-party resource access request, the second third-party resource access request comprising a second user identifier associated with a second user and the second third-party resource provider identifier; and

transmitting, to the second third-party resource provider, a second third-party resource user account creation request, the second third-party resource user account creation request comprising a second third-party resource access token.

4. The method of claim 3 , further comprising returning, as a result of searching a third-party resource usage map, an indicative third-party resource usage record associated with the second user identifier, the indicative third-party resource usage record comprising the second third-party resource provider identifier.

5. The method of claim 3 , wherein the second third-party resource user account creation request is a request to create a second third-party resource user account on behalf of the second client device.

6. The method of claim 1 , further comprising:

transmitting, to the first third-party resource provider, a first third-party resource user account creation request;

receiving, in response to the first third-party resource user account creation request, a first third-party resource user account creation approval; and

generating a new third-party resource usage record associated with the first user identifier.

7. The method of claim 6 , wherein the new third-party resource usage record comprises one or more of the first third-party resource provider identifier and the first third-party resource access token.

8. The method of claim 6 , further comprising including the new third-party resource usage record in a third-party resource usage map.

9. A system comprising:

one or more processors; and

computer readable media storing instructions that, when executed, cause the system to perform operations comprising:

receiving, from a first third-party resource provider, a first third-party resource access token;

receiving, from a first client device associated with a first user, a first third-party resource access request, the first third-party resource access request comprising a first user identifier and a first third-party resource provider identifier;

retrieving, based at least in part on receiving the first third-party resource access request and from a group-based communication repository maintained by a group-based communication platform, a plurality of third-party resource usage records, wherein individual ones of the plurality of third-party resource usage records are associated with a different user identifier;

determining that a second third-party resource provider identifier associated with a second third-party resource provider is absent from the plurality of third-party resource usage records; and

transmitting, to respective client devices associated with the individual ones of the plurality of third-party resource usage records, a recommendation to access a second third-party resource, wherein the recommendation to access the second third-party resource comprises the second third-party resource provider identifier.

10. The system of claim 9 , the operations further comprising:

receiving, from a second client device of the respective client devices and in response to a recommendation to access the second third-party resource, a second third-party resource access request, the second third-party resource access request comprising a second user identifier associated with a second user and the second third-party resource provider identifier; and

transmitting, to the second third-party resource provider, a second third-party resource user account creation request, the second third-party resource user account creation request comprising a second third-party resource access token.

11. The system of claim 10 , wherein the second third-party resource user account creation request is a request to create a second third-party resource user account on behalf of the second client device.

12. The system of claim 10 , the operations further comprising returning, as a result of searching a third-party resource usage map, an indicative third-party resource usage record associated with the second user identifier, the indicative third-party resource usage record comprising the second third-party resource provider identifier.

13. The system of claim 9 , the operations further comprising:

transmitting, to the first third-party resource provider, a first third-party resource user account creation request; and

receiving, in response to the first third-party user account creation request, a first third-party user account creation approval.

14. The system of claim 11 , the operations further comprising generating a new third-party resource usage record associated with the first user identifier.

15. One or more non-transitory computer readable media storing computer-executable instructions that, when executed by one or more processors of a computing device, cause the computing device to perform operations comprising:

receiving, from a first third-party resource provider, a first third-party resource access token;

receiving, from a first client device associated with a first user, a first third-party resource access request, the first third-party resource access request comprising a first user identifier and a first third-party resource provider identifier;

retrieving, based at least in part on receiving the first third-party resource access request and from a group-based communication repository maintained by a group-based communication platform, a plurality of third-party resource usage records, wherein individual ones of the plurality of third-party resource usage records are associated with a different user identifier;

determining that a second third-party resource provider identifier associated with a second third-party resource provider is absent from the plurality of third-party resource usage records; and

transmitting, to respective client devices associated with the individual ones of the plurality of third-party resource usage records, a recommendation to access a second third-party resource, wherein the recommendation to access the second third-party resource comprises the second third-party resource provider identifier.

16. The one or more non-transitory computer readable media of claim 15 , the operations further comprising:

receiving, from a second client device of the respective client devices and in response to a recommendation to access the second third-party resource, a second third-party resource access request, the second third-party resource access request comprising a second user identifier associated with a second user and the second third-party resource provider identifier; and

transmitting, to the second third-party resource provider, a second third-party resource user account creation request, the second third-party resource user account creation request comprising a second third-party resource access token.

17. The one or more non-transitory computer readable media of claim 16 , wherein the second third-party resource user account creation request is a request to create a second third-party resource user account on behalf of the second client device.

18. The one or more non-transitory computer readable media of claim 16 , the operations further comprising returning, as a result of searching a third-party resource usage map, an indicative third-party resource usage record associated with the second user identifier, the indicative third-party resource usage record comprising the second third-party resource provider identifier.

19. The one or more non-transitory computer readable media of claim 15 , the operations further comprising:

transmitting, to the first third-party resource provider, a first third-party resource user account creation request; and

receiving, in response to the first third-party resource user account creation request, a first third-party resource user account creation approval.

20. The one or more non-transitory computer readable media of claim 19 , the operations further comprising generating a new third-party resource usage record associated with the first user identifier.

Assignments (4)
MERGER Recorded Nov 21, 2022
From: SLACK TECHNOLOGIES, LLC
To: SALESFORCE.COM, INC.
Reel/Frame 061972/0569 →
CHANGE OF NAME Recorded Nov 21, 2022
From: SALESFORCE.COM, INC.
To: SALESFORCE, INC.
Reel/Frame 061972/0769 →
ASSIGNMENT OF ASSIGNOR'S INTEREST Recorded Sep 27, 2022
From: GAMACHE, MEAGAN; BENSON, BUSTER
To: SLACK TECHNOLOGIES, INC.
Reel/Frame 061231/0853 →
MERGER AND CHANGE OF NAME Recorded Sep 27, 2022
From: SLACK TECHNOLOGIES, INC.; SLACK TECHNOLOGIES, LLC
To: SLACK TECHNOLOGIES, LLC
Reel/Frame 061231/0932 →