# US 2021/0240729 A1 · Dynamic Profile Reconciliation In Group-Based Communication Systems > Agents: this data is available as JSON from the patentgrep API and MCP server — see https://patentgrep.com/llms.txt - Number: US 2021/0240729 A1 - Document ID: US20210240729A1 - Status: Published application - Kind: A1 - Application number: 17/156,916 - Filed: 2021-01-25 - Published: 2021-08-05 - Earliest claimed: 2020-01-31 - Assignees: Slack Technologies, LLC - Applicants: Slack Technologies, Inc. - Inventors: Myles Grant; Elizabeth Clemenson; Paul Rosania; Sri Vasamsetti; Yingyu Sun - Web page: https://patentgrep.com/patent/US20210240729A1 ## CPC - G06F 16/215: Improving data quality; Data cleansing, e.g. de-duplication, removing invalid entries or correcting typographical errors - G06F 16/27: Replication, distribution or synchronisation of data between databases or within a distributed database system; Distributed database system architectures therefor - G06F 16/25: Integrating or interfacing systems involving database management systems - H04L 51/216: Handling conversation history, e.g. grouping of messages in sessions or threads - H04L 67/306: User profiles - G06F: ELECTRIC DIGITAL DATA PROCESSING (computer systems based on specific computational models G06N) - H04L: TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION (arrangements common to telegraphic and telephonic communication H04M) ## Abstract Techniques for performing dynamic profile reconciliation in a communication system. A server computing system may identify two or more user profiles corresponding to a same user that is associated with the communication system. The server computing system may integrate historical data associated with the two or more user profiles into a single user profile (e.g., a destination user profile). The historical data may include messages sent and/or received via the two or more user profiles, files associated with the messages, metadata corresponding to each message, and the like. Responsive to combining the two or more user profiles into the single user profile, the server computing system may delete at least one of the two or more user profiles, storing the combined data in association with the single user profile. ## Claims ### Claim 1 An apparatus for profile reconciliation in a group-based communication system, the apparatus comprising at least one processor and at least one memory, the at least one memory having computer-coded instructions stored thereon, where the computer-coded instructions, in execution with the at least one processor, configure the apparatus to: identify an identity association between a source profile and a destination profile, wherein the source profile and the destination profile are associated with a same user identifier of the group-based communication system; based at least in part on the identity association, perform a cross-profile communication history integration between the source profile and the destination profile, wherein performing the cross-profile communication history integration causes the apparatus to: identify a source communication history stream associated with the source profile and a destination communication history stream associated with the destination profile; and integrate one or more source communication data objects of the source communication history stream into one or more destination communication data objects of the destination communication history stream based at least in part on temporal markers associated with the one or more source communication data objects and the one or more destination communication data objects; and in response to completing the cross-profile communication history integration between the source profile and the destination profile, deactivate the source profile. ### Claim 2 (depends on 1) The apparatus of claim 1, wherein: the source profile has a limited access privilege with respect to the group-based communication system; and the destination profile has full access privilege with respect to the group-based communication system. ### Claim 3 (depends on 1) The apparatus of claim 1, further configured to: receive a request to convert a non-shared communication channel into a shared communication channel; and identify a guest account associated with the non-shared communication channel, wherein the source profile corresponds to the guest account, wherein the identity association is identified based at least in part on the request and an identification of the guest account. ### Claim 4 (depends on 3) The apparatus of claim 3, wherein: the non-shared communication channel is associated with a primary organizational identifier, the shared communication channel is associated with the primary organizational identifier and a secondary organizational identifier; first content data associated with the non-shared communication channel is encrypted according to a first policy associated with the primary organizational identifier; and second content data associated with the shared communication channel is encrypted according to the first policy and a second policy associated with the secondary organizational identifier. ### Claim 5 (depends on 1) The apparatus of claim 1, further configured to: based at least in part on the identity association, modify a source ownership indicator of content data associated with the source profile to enable transfer of ownership of the content data to the destination profile. ### Claim 6 (depends on 1) The apparatus of claim 1, further configured to: generate a destination stream communication interface for the destination communication history stream, wherein the destination stream communication interface is configured to at least one of: be accessible by a client device associated with the destination profile; or display the destination communication history stream. ### Claim 7 (depends on 1) The apparatus of claim 1, further configured to: perform a cross-profile personal data integration for the source profile and the destination profile based at least in part on the identity association, wherein performing the cross-profile personal data integration causes the apparatus to: identify a personal data object associated with the source profile, the personal data object having associated with a user identifier indicating a source identifier associated with the source profile; and modify the user identifier of the personal data object to indicate a destination identifier associated with the destination profile. ### Claim 8 (depends on 1) The apparatus of claim 1, further configured to: perform a cross-profile data integration for the source profile and the destination profile based at least in part on the identity association, wherein performing the cross-profile data integration causes the apparatus to: identify a data object associated with the source profile, the data object having associated therewith a user identifier indicating a source identifier associated with the source profile; and modify the user identifier associated with the data object to indicate a destination identifier associated with the destination profile. ### Claim 9 A computer-implemented method for profile reconciliation in a communication system, the computer-implemented method comprising: identifying an identity association between a source profile and a destination profile, wherein the source profile and the destination profile are associated with a same user identifier of the communication system; based at least in part on the identity association, performing a cross-profile communication history integration between the source profile and the destination profile, wherein performing the cross-profile communication history integration comprises: identifying a source communication history stream associated with the source profile and a destination communication history stream associated with the destination profile; and integrating one or more source communication data objects of the source communication history stream into one or more destination communication data objects of the destination communication history stream based at least in part on temporal markers associated with the one or more source communication data objects and the one or more destination communication data objects; and in response to completing the cross-profile communication history integration between the source profile and the destination profile, deactivating the source. ### Claim 10 (depends on 9) The computer-implemented method of claim 9, wherein: the source profile has a limited access privilege with respect to the communication system; and the destination profile has full access privilege with respect to the communication system. ### Claim 11 (depends on 9) The computer-implemented method of claim 9, further comprising: receiving a request to convert a non-shared communication channel into a shared communication channel; and identifying a guest account associated with the non-shared communication channel, wherein the source profile corresponds to the guest account, wherein the identity association is identified based at least in part on the request and an identification of the guest account. ### Claim 12 (depends on 11) The computer-implemented method of claim 11, wherein: the non-shared communication channel is associated with a primary organizational identifier, the shared communication channel is associated with the primary organizational identifier and a secondary organizational identifier; first content data associated with the non-shared communication channel is encrypted according to a first policy associated with the primary organizational identifier; and second content data associated with the shared communication channel is encrypted according to the first policy and a second policy associated with the secondary organizational identifier. ### Claim 13 (depends on 9) The computer-implemented method of claim 9, further comprising: based at least in part on the identity association, modifying a source ownership indicator of content data associated with the source profile to enable transfer of ownership of the content data to the destination profile. ### Claim 14 (depends on 9) The computer-implemented method of claim 9, further comprising: generating a destination stream communication interface for the destination communication history stream, wherein the destination stream communication interface is configured to at least one of: be accessible by a client device associated with the destination profile; or display the destination communication history stream. ### Claim 15 (depends on 9) The computer-implemented method of claim 9, further comprising: performing a cross-profile data integration for the source profile and the destination profile based at least in part on the identity association, wherein performing the cross-profile data integration comprises: identifying a data object associated with the source profile, the data object having associated therewith a user identifier indicating a source identifier associated with the source profile; and modifying the user identifier associated with the data object to indicate a destination identifier associated with the destination profile. ### Claim 16 One or more non-transitory computer storage media comprising instructions for performing dynamic profile reconciliation in a communication system, the instructions being configured to cause one or more processors to perform operations comprising: identifying an identity association between a source profile and a destination profile, wherein the source profile and the destination profile are associated with a same user identifier of the communication system; based at least in part on the identity association, performing a cross-profile communication history integration between the source profile and the destination profile, wherein performing the cross-profile communication history integration comprises: identifying a source communication history stream associated with the source profile and a destination communication history stream associated with the destination profile; and integrating one or more source communication data objects of the source communication history stream into one or more destination communication data objects of the destination communication history stream based at least in part on temporal markers associated with the one or more source communication data objects and the one or more destination communication data objects; and in response to completing the cross-profile communication history integration between the source profile and the destination profile, deactivating the source profile. ### Claim 17 (depends on 16) The one or more non-transitory computer storage media of claim 16, wherein: the source profile has a limited access privilege with respect to the communication system; and the destination profile has full access privilege with respect to the communication system. ### Claim 18 (depends on 16) The one or more non-transitory computer storage media of claim 16, the operations further comprising: receiving a request to modify a non-shared communication channel into a shared communication channel; and identifying a guest account associated with the non-shared communication channel, wherein the source profile corresponds to the guest account, wherein the identity association is identified based at least in part on the request and an identification of the guest account. ### Claim 19 (depends on 18) The one or more non-transitory computer storage media of claim 18, wherein the non-shared communication channel is associated with a primary organizational identifier, the shared communication channel is associated with the primary organizational identifier and a secondary organizational identifier; first content data associated with the non-shared communication channel is encrypted according to a first policy associated with the primary organizational identifier; and second content data associated with the shared communication channel is encrypted according to the first policy and a second policy associated with the secondary organizational identifier. ### Claim 20 (depends on 16) The one or more non-transitory computer storage media of claim 16, the operations further comprising: based at least in part on the identity association, modifying a source ownership indicator of content data associated with the source profile to enable transfer of ownership of the content data to the destination profile.