INPUT_OBJECT

UpdateRegistrationConfiguration

link GraphQL Schema definition

1input UpdateRegistrationConfiguration {
3
2organizationGuid: ID
5
4name: String
7
6slug: String
18
8# When sent: the complete set of documents, replacing what is stored. A document
9# type left out,
10# or sent with status inactive, is retired and no longer shown to registrants; an
11# empty list
12# retires every document. Retired documents stay readable on
13# registrationConfiguration and are
14# reactivated by sending the same URL again. When omitted or null: the stored
15# documents are left
16# unchanged.
17files: [OrgFileResourceInput]
20
19openRegistrationStatus: OrgRegistrationStatus
22
21allowlistDomains: [String]
24
23adminApprovalRequired: Boolean
28
25# How registrants not on the access list are handled under restricted
26# registration. Omitted = unchanged.
27notOnListHandling: NotOnListHandling
30
29uiSettings: OrgUISettingsInput
41
31# When sent: the complete normal access list, replacing what is stored, on either
32# access-list
33# model. A legacy client may carry Default Access as an entry with domainName "".
34# The list must
35# contain at least one entry (a normal entry, or Default Access): an empty list is
36# rejected.
37# When omitted or null: the stored entries are left unchanged; on the new
38# access-list model they
39# are normally managed through the per-entry access-list APIs.
40domainSettings: [OrgDomainSettingsInput]
54
42# Default Access for registrants matching no entry: a grant sets or replaces it,
43# null clears it,
44# omitted leaves it unchanged. When domainSettings is also sent, defaultAccess
45# wins over a
46# domainName "" entry when both are present. When neither is present: on the
47# legacy access-list
48# model the list is the whole access state and Default Access is cleared; on the
49# new model, where
50# the domainSettings read never includes the "" row, the stored Default Access is
51# kept, and only an
52# explicit null clears it.
53defaultAccess: RegistrationAccessGrantInput
55}