Once a domain request has been adjudicated, the details of that request should not be modified. To update attributes (like an organization’s name) after a domain’s approval, - go to Domains. + go to Domains. Similar fields display on each Domain page, but edits made there will not affect the corresponding domain request.
{% elif opts.model_name == 'domaininformation' %} @@ -17,7 +17,7 @@ Domain information represents the basic metadata for an approved domain and the organization that manages it. It does not include any information specific to the registry (DNS name servers, security email). Registry-related information - can be managed within the Domains table. + can be managed within the Domains table.@@ -25,7 +25,7 @@
- Domain information is similar to Domain requests, + Domain information is similar to Domain requests, and the fields are nearly identical, but edits made to one are not made to the other. Domain information exists so we don’t modify details of an approved request after adjudication @@ -46,7 +46,7 @@
If an invitation is created in this table, an email will not be sent. - To have an email sent, go to the domain in Domains, + To have an email sent, go to the domain in Domains, click the “Manage domain” button, and add a domain manager.
{% elif opts.model_name == 'contact' %} @@ -54,7 +54,7 @@ Contacts include anyone who has access to the registrar (known as “users”) and anyone listed in a domain request, including other employees and authorizing officials. Only contacts who have access to the registrar will have - a corresponding record within the Users table. + a corresponding record within the Users table. Updating someone’s contact information here will not affect that person’s Login.gov information. {% elif opts.model_name == 'logentry' %} @@ -63,7 +63,7 @@ The table on this page is useful for searching actions across all records. To understand what happened to an individual record (like a domain request), it’s better to go to that specific page - (Domain requests) and click on the “History” button. + (Domain requests) and click on the “History” button. {% elif opts.model_name == 'domain'%}@@ -100,7 +100,7 @@
This table does not include “alternative domains,” - which are housed in the Websites table. + which are housed in the Websites table.
{% elif opts.model_name == 'host' %}@@ -111,7 +111,7 @@
In general, you should not modify these values here. They should be updated directly inside the registrar. To update a domain’s name servers and/or IP addresses, - in the registrar, go to the domain in Domains, + in the registrar, go to the domain in Domains, then click the "Manage domain" button.
{% elif opts.model_name == 'publiccontact' %} @@ -152,7 +152,7 @@ {% elif opts.model_name == 'usergroup' %}Groups are a way to bundle admin permissions so they can be easily assigned to multiple users. - Once a group is created, it can be assigned to people via the Users table. + Once a group is created, it can be assigned to people via the Users table.
@@ -174,7 +174,7 @@
Each user record displays the associated “contact” info for that user, - which is the same info found in the Contacts table. + which is the same info found in the Contacts table. Updating these details on the user record will also update the corresponding contact record for that user.
{% elif opts.model_name == 'verifiedbystaff' %} @@ -194,8 +194,8 @@- This does not include any “requested domains” that have appeared within the Domain requests table. - Those names are managed in the Draft domains table. + This does not include any “requested domains” that have appeared within the Domain requests table. + Those names are managed in the Draft domains table.
{% else %}This table does not have a description yet.