Organisation administration
Profile, retention policy and support access.
Why
Changes are reported field by field against what is currently held. A submission that changes nothing is refused.
Writes are validated against the engineering rules and then refused, because no database has been configured for this environment.
Projects
3
People
10
Retention policy
None agreed
Active support grants
0
Profile
Blank retention is not zero retention
Support access
A ZEMERC support principal holds an organisation role that carries nothing on its own. With no unexpired grant they can read nothing at all. A grant names a reason, is capped at twenty-four hours by a database constraint, permits reading and never writing, and is visible to you in the audit trail.
ZEMERC Support currently holds no project role and can see nothing.
Organisations in this instance
| Organisation | Role | Plan | People |
|---|---|---|---|
| ZEMERC Engineering | owner | enterprise | 9 |
| Reference Gas Operating Company | client | project | 1 |
| Caspian EPC Consortium | contractor | enterprise | 0 |
Changing the slug
It appears in every storage key, so a change is refused once a file exists. No store exists yet. Why