Abstract: A computing platform is configured to (i) receive configuration data defining a permissions group for a construction project, the configuration data indicating a data domain and a set of actions performable on data objects within the data domain that have a particular value for a particular data object attribute, (ii) after receiving the configuration data, receive a data access request, on behalf of a user account, for a data object within the data domain, (iii) determine that the user account is a member of the permissions group, (iv) determine that the data object has the particular data object attribute with the particular value and thereby satisfies the condition, and (v) based on determining that (a) the user account is a member of the permissions group and (b) the data object satisfies the condition, determine that the user account is permitted to perform the set of actions on the data object.

Abstract: A computing system that defines a first zone of a multi-zone computing platform is configured to (1) receive a request to access at least one given data object that is stored within the multi-zone computing platform, (2) obtain, from a global representation of available data that is stored within the multi-zone computing platform, a routing address that includes information indicating where the at least one given data object is stored, (3) validate the request to access the at least one given data object, (4) determine that the request is valid and should be allowed, (5) determine whether the at least one given data object is stored at the first zone, and (6) based on the determination, either retrieve the at least one given data object from the first zone or issue a request to retrieve the at least one given data object from a second zone.

Abstract: A computing system that defines a first zone of a multi-zone computing platform is configured to (1) receive a request to access at least one given data object that is stored within the multi-zone computing platform, (2) obtain, from a global representation of available data that is stored within the multi-zone computing platform, a routing address that includes information indicating where the at least one given data object is stored, (3) validate the request to access the at least one given data object, (4) determine that the request is valid and should be allowed, (5) determine whether the at least one given data object is stored at the first zone, and (6) based on the determination, either retrieve the at least one given data object from the first zone or issue a request to retrieve the at least one given data object from a second zone.

Abstract: A computing platform is configured to (i) receive configuration data defining a permissions group for a construction project, the configuration data indicating a data domain and a set of actions performable on data objects within the data domain that have a particular value for a particular data object attribute, (ii) after receiving the configuration data, receive a data access request, on behalf of a user account, for a data object within the data domain, (iii) determine that the user account is a member of the permissions group, (iv) determine that the data object has the particular data object attribute with the particular value and thereby satisfies the condition, and (v) based on determining that (a) the user account is a member of the permissions group and (b) the data object satisfies the condition, determine that the user account is permitted to perform the set of actions on the data object.

Abstract: Techniques for managing data and data connections for a construction project involve (1) establishing respective data connections between (i) each party-entity data record and a project-entity data record for the construction project, and (ii) each party-entity data record and each respective object-entity data record for the construction project, (2) determining each party's permissions for retaining access to (i) the project-entity data record and (ii) each object-entity data record after a trigger event occurs, and (3) generating (i) respective connection data encoding the party's permissions for retaining access to the project-entity data record to be stored in association with the respective data connection between the party-entity data record and the project-entity data record and (ii) respective connection data encoding the party's permissions for retaining access to each respective object-entity data record in association with the respective data connection between the party-entity data record and the

Abstract: A computing system that defines a first zone of a multi-zone computing platform is configured to (1) receive a request to access at least one given data object that is stored within the multi-zone computing platform, (2) obtain, from a global representation of available data that is stored within the multi-zone computing platform, a routing address that includes information indicating where the at least one given data object is stored, (3) validate the request to access the at least one given data object, (4) determine that the request is valid and should be allowed, (5) determine whether the at least one given data object is stored at the first zone, and (6) based on the determination, either retrieve the at least one given data object from the first zone or issue a request to retrieve the at least one given data object from a second zone.

Abstract: Disclosed herein is software technology that enables different accounts to be mirrored. In one aspect, the disclosed process may involve determining that an origin data record created under a first account of a first party is to be mirrored to a second account of a second party, generating a thread identification that is mapped to the data record created under the first account of the first party, and generating a first message that comprises data from the origin data record and the thread identifier that is mapped to the origin data record. Based on the first message, the disclosed process may further involve creating a target data record under a second account of a second party that corresponds to the origin data record created under the first account of the first party and storing the target data record under the second account of the second party.

Abstract: Disclosed herein is software technology that enables different accounts to be mirrored. In one aspect, the disclosed process may involve determining that an origin data record created under a first account of a first party is to be mirrored to a second account of a second party, generating a thread identification that is mapped to the data record created under the first account of the first party, and generating a first message that comprises data from the origin data record and the thread identifier that is mapped to the origin data record. Based on the first message, the disclosed process may further involve creating a target data record under a second account of a second party that corresponds to the origin data record created under the first account of the first party and storing the target data record under the second account of the second party.

Abstract: A computing system configured to: (i) receive a request to create a project entity; create the project entity; establish a data connection between a first party and the project entity; and define the first party's default data retention settings; (ii) receive a request to create a set of data objects associated with the project entity; create each data object in the set; establish a respective data connection between the first party and each data object; and define the first party's data retention settings for the respective data object; (iii) after receiving an indication that a second party has accepted the first party's invitation to collaborate: establish a data connection between the second party and the project entity; define the second party's default data retention settings; establish a respective data connection between the second party and each data object; and define the second party's data retention settings for each data object to match the second party's default data retention settings.

Abstract: Systems and methods for managing access to data stored in a distributed manner across different zones of a multi-zone computing platform involve maintaining a global representation of all data stored within the multi-zone computing platform. After receiving a request on behalf of a user to access given data, a first zone of the multi-zone computing platform (i) obtains, from the global representation, information indicating a particular zone where the given data is stored, (ii) validates the request, and (iii) if the validation is successful, processes the request. If the given data is stored at the first zone, the first zone retrieves the given data for provision to the user. If the given data is stored at a second zone, the first zone issues a request to the second zone to validate the request, and if the validation is successful, retrieve the given data for provision to the user.

Abstract: A computing system that defines a first zone of a multi-zone computing platform is configured to: receive a request to access at least one given data object that is stored within the multi-zone computing platform; obtain, from a global representation of available data that is stored within the multi-zone computing platform, a routing address that includes information indicating where the at least one given data object is stored; perform one or more validation operations on the request to access the at least one given data object; determine that the request is valid and should be allowed; make a determination of whether the at least one given data object is stored at the first zone; and based on the determination, either retrieve the at least one given data object from the first zone or issue a request to retrieve the at least one given data object from a second zone.

Abstract: Disclosed herein is software technology that enables different accounts to be mirrored. In one aspect, the disclosed process may involve determining that an origin data record created under a first account of a first party is to be mirrored to a second account of a second party, generating a thread identification that is mapped to the data record created under the first account of the first party, and generating a first message that comprises data from the origin data record and the thread identifier that is mapped to the origin data record. Based on the first message, the disclosed process may further involve creating a target data record under a second account of a second party that corresponds to the origin data record created under the first account of the first party and storing the target data record under the second account of the second party.

Abstract: A computing system configured to: (i) receive a request to create a project entity; create the project entity; establish a data connection between a first party and the project entity; and define the first party's default data retention settings; (ii) receive a request to create a set of data objects associated with the project entity; create each data object in the set; establish a respective data connection between the first party and each data object; and define the first party's data retention settings for the respective data object; (iii) after receiving an indication that a second party has accepted the first party's invitation to collaborate: establish a data connection between the second party and the project entity; define the second party's default data retention settings; establish a respective data connection between the second party and each data object; and define the second party's data retention settings for each data object to match the second party's default data retention settings.

Abstract: Disclosed herein is software technology that enables different accounts to be mirrored. In one aspect, the disclosed process may involve determining that an origin data record created under a first account of a first party is to be mirrored to a second account of a second party, generating a thread identification that is mapped to the data record created under the first account of the first party, and generating a first message that comprises data from the origin data record and the thread identifier that is mapped to the origin data record. Based on the first message, the disclosed process may further involve creating a target data record under a second account of a second party that corresponds to the origin data record created under the first account of the first party and storing the target data record under the second account of the second party.

Abstract: Disclosed herein is software technology that enables different accounts to be mirrored. In one aspect, the disclosed process may involve determining that an origin data record created under a first account of a first party is to be mirrored to a second account of a second party, generating a thread identification that is mapped to the data record created under the first account of the first party, and generating a first message that comprises data from the origin data record and the thread identifier that is mapped to the origin data record. Based on the first message, the disclosed process may further involve creating a target data record under a second account of a second party that corresponds to the origin data record created under the first account of the first party and storing the target data record under the second account of the second party.