Database object mastership

For user database records, mastership information is stored as a field value in a record. Users can change the value of the mastership field to transfer mastership to another replica. Mastership of the record is sent to the new master replica during the next synchronization. For all other database objects, an administrator must change the mastership.

The following objects have a master replica:
  • Records
  • Users and groups
  • Workspace items (queries, reports, charts, and folders)
  • Schema repository

When you work in a MultiSite environment, you must adjust your workflow to account for any stage in your software lifecycle that requires a change of mastership for a record or defect.

For example, users in Paris can submit defects that should be worked on by developers in Boston. But without a change of mastership, developers in Boston cannot modify defects entered by users in Paris.