You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
It would be good for each deployment to have a contact email defined, ideally in a form that can be easily accessed via the API. This could be added to the configuration, saved on the metadata server and made accessible through the API
The text was updated successfully, but these errors were encountered:
@davidorme suggested that this would make more sense as a config option for safedata_server. With the following caveat, "But... there should be a docs section for setup that goes through those bits and makes sure admins set it up right." So, this is a documentation change rather than a code change
It would be good for each deployment to have a contact email defined, ideally in a form that can be easily accessed via the API. This could be added to the configuration, saved on the metadata server and made accessible through the API
The text was updated successfully, but these errors were encountered: