IP Library Granted Patent US 11,487,399
Granted Patent B2
US 11,487,399 · App. 17/582,318 · Granted Nov 1, 2022

Method, apparatus and computer program product for providing a member calendar in a group-based communication system

Inventors: Lydia Han (San Francisco, CA); Roland Schemers (Woodside, CA)
Assignee: SlackTechnologies, LLC
G06F3/0481G06F3/04847G06Q10/1095G06F2203/04803H04L67/306
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,487,399
App. No.
17/582,318
Granted
Nov 1, 2022
Kind
B2
Abstract

Method, apparatus and computer program product for generating a member calendar in a group-based communication system are described herein.

Claims (53)

1. A method for sharing a calendar object in a group-based communication system, the method comprising:

receiving, via a first device, at least one message associated with a group of users in a first user interface associated with a first user in the group-based communication system,

said group-based communication system comprising a plurality of group-based communication channels, each channel configured to display a plurality of messages from a plurality of users in the first user interface;

automatically determining at least one parameter of an event object based on content of the at least one message in the first user interface of the group-based communication system;

transmitting, via the group-based communication system, a validation request to an external calendar resource to access the calendar object associated with the group of users;

receiving a validation notification from the external calendar resource;

retrieving the calendar object associated with the group of users from the external calendar resource; and

rendering, in the first user interface, the calendar object associated with the group of users to include the event object.

2. The method of claim 1 , further comprising:

rendering a calendar object associated with the first user and the calendar object associated with the group of users for display simultaneously in the first user interface.

3. The method of claim 1 , wherein the event object comprises a visibility parameter, further comprising:

rendering the calendar object based at least in part on the visibility parameter.

4. The method of claim 3 , wherein if the visibility parameter is private, further comprising:

preventing display of the event object in the first user interface.

5. The method of claim 1 , wherein the event object comprises an availability parameter, further comprising:

rendering the calendar object based at least in part on the availability parameter.

6. The method of claim 1 , wherein the first user interface comprises at least one channel displaying a messaging interface.

7. The method of claim 1 , wherein the group of users comprises a team having a shared channel.

8. An apparatus configured to share a calendar object in a group-based communication system, the apparatus comprising at least a processor, and a memory associated with the processor having computer coded instructions therein, with the computer coded instructions configured to, when executed by the processor, cause the apparatus to:

receive, via a first device, at least one message associated with a group of users in a first user interface associated with a first user in the group-based communication system,

wherein said group-based communication system comprises a plurality of group-based communication channels, each channel configured to display a plurality of messages from a plurality of users in the first user interface;

automatically determine at least one parameter of an event object based on content of the at least one message in the first user interface of the group-based communication system;

transmit, via the group-based communication system, a validation request to an external calendar resource to access the calendar object associated with the group of users,

receive a validation notification from the external calendar resource;

retrieve the calendar object associated with the group of users from the external calendar resource; and

render, in the first user interface, the calendar object associated with the group of users to include the event object.

9. The apparatus of claim 8 , wherein the apparatus is further caused to:

render a calendar object associated with the first user and the calendar object associated with the group of users for display simultaneously in the first user interface.

10. The apparatus of claim 8 , wherein the event object comprises a visibility parameter, and the apparatus is further caused to:

render the calendar object based at least in part on the visibility parameter.

11. The apparatus of claim 10 , wherein if the visibility parameter is private, the apparatus is further caused to:

prevent display of the event object in the first user interface.

12. The apparatus of claim 8 , wherein the event object comprises an availability parameter, and the apparatus is further caused to:

render the calendar object based at least in part on the availability parameter.

13. The apparatus of claim 8 , wherein the first user interface comprises at least one channel displaying a messaging interface.

14. The apparatus of claim 8 , wherein the group of users comprises a team having a shared channel.

15. A non-transitory computer-readable storage medium including instructions to share a calendar object in a group-based communication system that when executed by a computer, cause the computer to:

receive, via a first device, at least one message associated with a group of users in a first user interface associated with a first user in the group-based communication system,

wherein said group-based communication system comprises a plurality of group-based communication channels, each channel configured to display a plurality of messages from a plurality of users in the first user interface;

automatically determine at least one parameter of an event object based on content of the at least one message in the first user interface of the group-based communication system;

transmit, via the group-based communication system, a validation request to an external calendar resource to access the calendar object associated with the group of users,

receive a validation notification from the external calendar resource;

retrieve the calendar object associated with the group of users from the external calendar resource; and

render, in the first user interface, the calendar object associated with the group of users to include the event object.

16. The medium of claim 15 , wherein the computer is further caused to:

render a calendar object associated with the first user and the calendar object associated with the group of users for display simultaneously in the first user interface.

17. The medium of claim 15 , wherein the event object comprises a visibility parameter, and the computer is further caused to:

render the calendar object based at least in part on the visibility parameter.

18. The medium of claim 17 , wherein if the visibility parameter is private, the computer is further caused to:

prevent display of the event object in the first user interface.

19. The medium of claim 15 , wherein the event object comprises an availability parameter, and the computer is further caused to:

render the calendar object based at least in part on the availability parameter.

20. The medium of claim 15 , wherein the group of users comprises a team having a shared channel.

Assignments (3)
ASSIGNMENT OF ASSIGNOR'S INTEREST Recorded Aug 18, 2023
From: SLACK TECHNOLOGIES, LLC
To: SALESFORCE, INC.
Reel/Frame 064642/0564 →
ASSIGNMENT OF ASSIGNOR'S INTEREST Recorded Jan 24, 2022
From: HAN, LYDIA; SCHEMERS, ROLAND
To: SLACK TECHNOLOGIES, INC.
Reel/Frame 058742/0105 →
MERGER Recorded Jan 24, 2022
From: SLACK TECHNOLOGIES, INC.
To: SLACK TECHNOLOGIES, LLC
Reel/Frame 058742/0189 →
Continuity (2)
Continuation 16398166 · Apr 29, 2019
Related Publication 20220147198A1 · May 12, 2022