Sharing customer data between entities in an organization
A server can adjust access privileges of a customer object of a first entity to provide access to the customer object to a second entity that is associated with the first entity in an organizational data structure, resulting in a shared customer object. An operation request can be received which is associated with the second entity with regard to the shared customer object. An option to associate at least one account object of the first entity to the shared customer object may be provided. After receiving an indication to associate the at least one account object to the shared customer object, the operation request may be executed using the at least one account object.
1 . A method comprising:
adjusting, by a server, access privileges of a customer object of a first entity to provide shared access to the customer object to a second entity that is associated with the first entity in an organizational data structure, wherein the first entity comprises an organization identifier corresponding to the organizational data structure, wherein the second entity comprises the organization identifier, wherein the customer object has associated therewith at least one account object, the at least one account object including one or more features associated therewith;
receiving, at the server, an operation request associated with the second entity with regard to the shared customer object;
providing, by the server, an option to associate the at least one account object to the shared customer object; and
after receiving an indication to associate the at least one account object to the shared customer object, executing, by the server, the operation request using the at least one account object.
2 . The method of claim 1 , further comprising:
associating a first modality of the at least one account object with the shared customer object of the second entity, while forgoing associating a second modality of the at least one account object with the shared customer object.
3 . The method of claim 2 , wherein the first modality corresponds to a first authorized mode of payment associated with the at least one account object, wherein the second modality corresponds to a second authorized mode of payment associated with the at least one account object.
4 . The method of claim 1 , wherein the first entity is designated as a primary entity for the customer object, wherein a designation of primary entity provides exclusive access rights to modify all aspects of corresponding customer objects.
5 . The method of claim 4 , further comprising:
receiving an update to the customer object, the update associated with the first entity; and
applying the update to the customer object based at least in part on the first entity being designated as the primary entity.
6 . The method of claim 4 , further comprising:
receiving an update to the customer object, the update associated with the second entity; and
forgoing applying the update to the customer object based at least in part on the first entity being designated as the primary entity.
7 . The method of claim 6 , further comprising:
requesting permission to modify the customer object from the first entity; and
upon receiving permission to modify the customer object, applying the update to the customer object.
8 . The method of claim 4 , further comprising:
receiving a request to designate the second entity as the primary entity for the customer object; and
designating the second entity as the primary entity for the customer object.
9 . A server comprising:
a non-transitory computer readable medium storing instructions; and
one or more processors configured to execute the instructions to:
adjust, by the server, access privileges of a customer object of a first entity to provide shared access to the customer object to a second entity that is associated with the first entity in an organizational data structure, wherein the first entity comprises an organization identifier corresponding to the organizational data structure, wherein the second entity comprises the organization identifier, wherein the customer object has associated therewith at least one account object, the at least one account object including one or more features associated therewith;
receive, at the server, an operation request associated with the second entity with regard to the shared customer object;
provide, by the server, an option to associate the at least one account object to the shared customer object; and
after receiving an indication to associate the at least one account object to the shared customer object, execute, by the server, the operation request using the at least one account object.
10 . The server of claim 9 , wherein the one or more processors are further configured to:
associate a first modality of the at least one account object with the shared customer object of the second entity, while forgoing associating a second modality of the at least one account object with the shared customer object.
11 . The server of claim 9 , wherein the one or more processors are further configured to:
receive an update to the customer object, the update associated with the first entity, and
apply the update to the customer object based at least in part on the first entity being designated as a primary entity.
12 . The server device of claim 9 , wherein the one or more processors are further configured to:
receive an update to the customer object, the update associated with the second entity;
forgo applying the update to the customer object based at least in part on the first entity being designated as a primary entity;
request permission to modify the customer object from the first entity; and
upon receiving permission to modify the customer object, apply the update to the customer object.
13 . A non-transitory computer-readable medium storing a set of instructions which when executed cause one or more processors to:
adjust, by a server, access privileges of a customer object of a first entity to provide shared access to the customer object to a second entity that is associated with the first entity in an organizational data structure, wherein the first entity comprises an organization identifier corresponding to the organizational data structure, wherein the second entity comprises the organization identifier, wherein the customer object has associated therewith at least one account object, the at least one account object including one or more features associated therewith;
receive, at the server, an operation request associated with the second entity with regard to the shared customer object;
provide, by the server, an option to associate the at least one account object to the shared customer object; and
after receiving an indication to associate the at least one account object to the shared customer object, execute, by the server, the operation request using the at least one account object.
14 . The non-transitory computer-readable medium of claim 13 , wherein the one or more instructions further cause the one or more processors to:
associate a first modality of the at least one account object with the shared customer object of the second entity, while forgoing associating a second modality of the at least one account object with the shared customer object.
15 . The non-transitory computer-readable medium of claim 14 , wherein the first modality corresponds to a first authorized mode of payment associated with the at least one account object, the second modality corresponds to a second authorized mode of payment associated with the at least one account object.
16 . The non-transitory computer-readable medium of claim 13 , wherein the first entity is designated as a primary entity for the customer object, a designation of primary entity provides exclusive access rights to modify all aspects of corresponding customer objects.
17 . The non-transitory computer-readable medium of claim 16 , wherein the one or more instructions further cause the one or more processors to:
receive an update to the customer object, the update associated with the first entity; and
apply the update to the customer object based at least in part on the first entity being designated as the primary entity.
18 . The non-transitory computer-readable medium of claim 16 , wherein the one or more instructions further cause the one or more processors to:
receive an update to the customer object, the update associated with the second entity; and
forgo applying the update to the customer object based at least in part on the first entity being designated as the primary entity.
19 . The non-transitory computer-readable medium of claim 18 , wherein the one or more instructions further cause the one or more processors to:
request permission to modify the customer object from the first entity; and
upon receiving permission to modify the customer object, apply the update to the customer object.
20 . The non-transitory computer-readable medium of claim 16 , wherein the one or more instructions further cause the one or more processors to:
receive a request to designate the second entity as the primary entity for the customer object; and
designate the second entity as the primary entity for the customer object.