| HTML |
|---|
<div id="google_translate_element"></div>
<script type="text/javascript">
function googleTranslateElementInit() {
new google.translate.TranslateElement({pageLanguage: 'en'}, 'google_translate_element');
}
</script>
<script type="text/javascript" src="//translate.google.com/translate_a/element.js?cb=googleTranslateElementInit"></script> |
ProVision First Steps
| Table of Contents |
|---|
...
In ProVision, standard user permissions are set by resource and functional area (IPAM, DNS, Peering, etc). Global Admin permissions give access to additional functions such as configuration settings, DNS management, Importing, and Scheduler Tasks. Determine which users will require administrative access, and which will have access to only specific resources or functional areas. You will need to get more specific later, but having some high level groups to work with is a great start.
See: Users & and Permissions
Overview Video: First Steps - Part 2
...
- Imports using the named.conf configuration file tied to the zones you are uploading, a .zip or .tar file of the zones themselves, and an optional .csv file mapping zones to customers and DNS Servers. See: BIND DNS Zone Upload / Import
DynECT Zone Import
- Imports and syncs ALL zones on the system with those in your DnyECT instance. This means any zones in ProVision not present in your DynECT instance will be removed and any changes lost. See: DynECT Zone Import
...
- Internal Users and Roles (Admins, Read Only, etc.)
- Partners related to multiple specific Resources/Accounts
- Customers/Departments with limited view to only their respective Resources/Accounts
See: Users & and Permissions, Users and Groups
Working In Provision
With the basic data now imported, and users set up, you (and your team) are ready to work in ProVision!
...
...