---
layout: article
title: Admin Services
description: The Administrator Screen provides useful system information and buttons for various administrator actions
og_title: Administrator Screen
og_image: /img/admininfo.png
---

## Administrator Screen

The admin screen (under user profile / System) displays a number of useful system parameters as well as several buttons for executing administrator specific actions

![](./img/admininfo.png)

Button info as follows:

|Button|Description|
|---|---|
|Refresh Data Lineage|This is only displayed for SAS9 installs.  Will refresh all TABLE level data lineage (impact analysis) using an efficient batch approach (proc metadata).|
|Refresh Data Catalog|Update Data Catalog for ALL libraries.  More info [here](/dcu-datacatalog).|
|Download Configuration|This downloads a zip file containing the current database configuration - useful for migrating to a different data controller database instance.|
|Update Licence Key| Link to the screen for providing a new Data Controller licence key|
|Export DC Library DDL|COMING SOON!!  <br>Exports the data controller control library in DB specific DDL (eg SAS, PGSQL, TSQL) and allows an optional schema name to be included|

## Licence Key Screen

The licence key screen accepts a Data Controller licence key and activation key.  The following features are available:

* **Combined-key paste** - paste a multi-field licence key (prefixed `DCKEY1:`) into either the licence key field or the dedicated combined-key input, and both the licence key and activation key are populated automatically.  The key format can be toggled between combined and legacy two-field input.
* **Live key preview** - as soon as both fields are populated, the key is decrypted speculatively and its details (valid until, number of users, feature flags, etc.) are displayed before you click Apply, so you can verify the key is correct.
* **Protocol mismatch guard** - if you paste a key generated for a different protocol than the page is currently using (http vs https), the Apply button is blocked and a warning is shown.  A key generated for an insecure connection carries the same text in both fields; a key generated for a secure connection carries two different values, so the mismatch can be detected before any decrypt attempt.