Holding Tank Management
How it Works
The "Process Holding Tank now" link will move any block assigned to "Holding" to its relevant "Available" pool. This command will process ALL addresses assigned to "Holding" depending on their age. The default time for release to "Available" is 30 days. If a block has not been in the holding tank for that specified length of time, it will not be released using this feature (it can be released manually per record at any time) . The threshold for the number of days in the Holding Tank is set in the main Admin Preferences page and is customizable.
When an administrator elects to process the Holding Tank, it will show the information above.
Pro-Tip!
If you need to do a bulk "empty" of the holding tank. Set the time for release to "0" days. This will allow you to process the holding tank for all blocks that are in the Holding Tank.
Holding Tank Permissions
For blocks with subassignments, the Holding Tank can utilize ProVision's permissions structure in order to override holding. This allows the subbassigned block to be set as assigned to the parent resource.
Using this feature requires:
1) A block (block 1) assigned to a Resource (Resource A) that allows subassignments.
2) A block (block 2) subassigned to another Resource (Resource B) from the parent (block 1).
3) A User assigned to a Group with permissions to both Resource A and Resource B, and IPAM permissions for the 6connect Holding Resource. See Users and Groups for additional information on setting up Users and Group permissions.
Steps:
1) While logged in as the user with the above permissions, go to the IPAM manage screen for the subassigned block (block 2).
2) Select "Unassign" from the Action Menu. The 'Assigned To' column will change from showing "Resource B" to "Holding"
3) For the same block, select "Override Holding" from the Action Menu. This is the step that setting the 6connect Holding resource permissions allows, that would otherwise be unaccessible.
4) You will then see the 'Assigned To' field change from "Holding" to "Resource A", as the assignment is reverted to match the parent level.
Override Holding through the permissions structure is intended only for blocks that are subassigned. It is not intended for blocks that are not subassigned. Setting holding permissions for non-subassigned blocks simply allows viewing of the block(s) in holding, and permissions do -not- extend to allowing overrides by design.