Working with Resources


What is a Resource?

The "Resource" system is tied to the Permissions structure. What this means is that you get granular control on a resource level and can create groups around a single resource or even groups of resources. Since Resources can inherit permissions from others - it can be an easy way to categorize generic objects.

WARNING!

There are key Resources that are used by the System that should not be deleted. We have put in some safeguards in the UI, but the API can delete these resources if prompted. The resources that you should not remove are "Holding" and "Reverse". The "Available" Resource can be renamed - simply not deleted.


How to Work with Resources?

The Resource is an entity that users can assign Network Resources to (IP blocks, hosts, DNS zones, etc.). You can also create hierarchies between resources which allows you to leverage permissions to control who can view and interact with any given resource and its assigned elements. Please note that you can also have Resources that do NOT have anything assigned to them regarding Network Resources. The result of this flexible architecture is that you can work with Resources in three ways:

  • Resource Entries: 
    These are the actual Resource names. When you click the "Add Entry" button you can customize various elements of the entry and assign the Parent Resource, Section and Category from their respective dropdown menus. You may also add a Custom ID if desired. 
    When done, hitting "Create"  will pull up the field set for the chosen Section and allow you to enter the data for the given Entry.
  • Resource Sections: 
    These can be anything from "customers" to "firewalls" to "cross-connects". Since you can customize the fields for these elements, and assign them to a Parent Section, you have flexibility in organizing the data. Check out Customizing Sections and Customizing Fields for more details on how to fit these elements to your business.

  • Resource Categories: 
    Categories can be used to create some filtered views for given Resources and Sections. For example, you can create a Section called "Resource Holder" and then assign a Category "Customer". Then you can view a list of Resources that have been assigned to Category "Customer". In the same way, you could also assign a Section called "Router" under the Parent Resource "Corporate Datacenter" and then assign a Category "Infrastructure".

Want to customize Sections? Check out Customizing Sections and Customizing Fields for more details!

Some examples:

1) Service Provider

2) Managed Service Provider

3) Datacenter/Colocation Provider

4) Enterprise


Additional Information

  • No labels