Allocation is how you hand seat inventory down to the sub-accounts beneath you, so they can run their own users independently. It’s the mechanism that powers the Siperb tree \u2014 departments that manage their own staff, resellers that manage their own clients, or any organisation where separate branches need their own seat supply.<\/p>\n\n\n\n
When you allocate seats to a sub-account, those seats move from your Available<\/strong> count into that sub-account’s inventory as Available<\/strong> \u2014 ready for them to assign to their own users. You remain the owner throughout. Allocation moves where a seat is held<\/em>; it never changes who owns and pays for it.<\/p>\n\n\n\n You own 10 Domain User seats. You manage three departments, each run by a branch head. You allocate 3 seats to Department A, 3 to Department B, and 2 to Department C \u2014 keeping 2 in reserve for yourself.<\/p>\n\n\n\n Your inventory now shows: Owned: 10 \/ Allocated: 8 \/ Available: 2<\/strong>. Each department head sees their allocated seats as Available in their own inventory and can assign them to their team members without needing to come back to you. Department A’s branch head decides to allocate 1 of their 3 seats down to a sub-account of their own \u2014 this is onward allocation, and it works the same way.<\/p>\n\n\n\n A sub-account that has received an allocation can onward-allocate those seats further down their own tree. This is what makes deep organisational structures work \u2014 a regional manager allocates seats to their site managers, who allocate to their teams, and so on. Ownership never changes hands; only the holding location does.<\/p>\n\n\n\n To reduce an allocation, lower the number and confirm. The freed seats return to your Available<\/strong> count immediately. If the sub-account is currently using more seats than your new allocation number, the Control Panel will block the reduction and ask you to free those users first \u2014 it will never pull a seat from under a live user.<\/p>\n\n\n\n Allocation is how you hand seat inventory down to the sub-accounts beneath you, so they can run their own users independently. It’s the mechanism that powers the Siperb tree \u2014 departments that manage their own staff, resellers that manage their own clients, or any organisation where separate branches need their own seat supply. How allocation…<\/p>\n","protected":false},"author":0,"featured_media":0,"comment_status":"closed","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"_kad_post_transparent":"","_kad_post_title":"","_kad_post_layout":"normal","_kad_post_sidebar_id":"","_kad_post_content_style":"","_kad_post_vertical_padding":"","_kad_post_feature":"hide","_kad_post_feature_position":"","_kad_post_header":false,"_kad_post_footer":false,"_kad_post_classname":"","footnotes":""},"categories":[21],"tags":[],"class_list":["post-14056","post","type-post","status-publish","format-standard","hentry","category-admin-control-panel"],"yoast_head":"\n\n
A worked example<\/h2>\n\n\n\n
Onward allocation<\/h2>\n\n\n\n
Key rules<\/h2>\n\n\n\n
\n
Reducing an allocation<\/h2>\n\n\n\n