Sharing Examples

From a plan designer's point of view, sharing seems as simple as two plan settings. For a tenant that allows multiple subscribers in an account, the Shareable/Assignable setting of a plan or bundle determines whether or not it can be shared among subscribers in the account. And if a plan or bundle can be shared, the Share Type setting determines whether the sharing occurs automatically or manually. But what happens to subscriber allocations when either the allocations are re-allocated or when a plan or bundle is upgraded or downgraded? The answer depends on the combination of these two settings. There are several events to consider:

Initial allocation: When the plan or bundle is first purchased, the default allocation at the time of purchase. (Purchaser can change allocations before proceeding to buy.)
Allocation change: When subscriber allocation is changed any time after plan or bundle purchase or receipt.
Subscriber join: When a subscriber joins (is added to) the account.
Subscriber unjoin: When a subscriber unjoins (is removed from) the account.
Downgrade: When the plan or bundle is exchanged for one with less total allowance.
Upgrade: When the plan or bundle is exchanged for one with more total allowance.

Sharing scenarios are viable only when the tenant offers more than one subscriber per account.

Sharing Combinations

With 2 Share Method options that enable sharing and with 2 Share Type options, there are 4 setting combinations to consider:

Share Method →	Automatic	Manual
Share Type ↓	Automatic	Manual
Piñata	Individual allocations can be up to 100%, the total of all subscriber allocations can be more than 100%, and subscriber allocations are automatically adjusted.	Individual allocations can be up to 100%, the total of all subscriber allocations can be more than 100%, and subscriber allocations are set explicitly.
Limited	Individual allocations can be up to 100%, the total of all subscriber allocations can not be more than 100%, and subscriber allocations are automatically adjusted.	Individual allocations can be up to 100%, the total of all subscriber allocations can not be more than 100%, and subscriber allocations are set explicitly.

The following sections describe how allocations are affected be events for each of these combinations.

Share Automatically: Piñata

With a Share Method setting of Automatic and a Share Type setting of Piñata, this is how plan and bundle allocation behaves.

Initial Allocation

Each subscriber in the account gets allocated 100%. The purchaser/account controller can change the initial allocation from the default before completing the purchase.

Allocation Change

The account controller changes subscriber allowances.

Subscriber allowances can be changed at any time to any whole number percentage from 0% to 100%.
The total of individual allowance percentage can be greater than 100%.
If a subscriber's current cycle usage exceeds the new allowance, the subscriber will have no more usage for the current cycle.

The following examples assume you start with a 500MB data plan with 3 subscribers sharing it.

Allocation Change Example 1

Subscriber A was allocated 40% (200MB) and has consumed 2% (10MB).
Subscriber B was allocated 80% (400MB) and has consumed 19.8% (99MB).
Subscriber C was allocated 20% (100MB) and has consumed 0% (0MB).
Total consumption during the cycle: 109MB, leaving 391MB.

The account controller changes subscriber B's allocation from 80% (400MB) to 20% (100MB) and subscriber C's allocation from 20% (100MB) to 40% (200MB).

Subscriber A's allocation and remaining usage does not change.
Subscriber B's allocation changes from 80% (400MB) to 20% (100MB). Usage for the cycle is now recorded as 99/100, so subscriber B has 1MB left to consume this cycle. In subsequent cycles, subscriber B will continue to have a 20% allocation of the plan allotment.
Subscriber C's allocation changes from 20% (100MB) to 40% (200MB). Usage for this cycle is now recorded as 0/200, so subscriber C has 200MB left to consume this cycle. In subsequent cycles, subscriber C will continue to have a 40% allocation of the plan allotment.
Total consumption during the cycle: 109MB. There is 391MB remaining for subscribers A, B, and C to share. Subscriber A can use up to 190MB more, subscriber B can use up to 1MB more, and subscriber C can use up to 200MB more.

Allocation Change Example 2

Subscriber A was allocated 40% (200MB) and has consumed 2% (10MB).
Subscriber B was allocated 80% (400MB) and has consumed 50% (200MB).
Subscriber C was allocated 20% (100MB) and has consumed 0% (0MB).
Total consumption during the cycle: 201MB, leaving 299MB.

The account controller changes subscriber B's allocation from 80% (400MB) to 20% (100MB) and subscriber C's allocation from 20% (100MB) to 40% (200MB).

Subscriber A's allocation and remaining usage does not change.
Subscriber B's allocation changes from 80% (400MB) to 20% (100MB). Because subscriber B's current cycle usage has already exceeded the new allocation, usage for the cycle is now recorded as 100/100, and subscriber B has 0MB left to consume this cycle. In subsequent cycles, subscriber B will continue to have a 20% allocation of the plan allotment.
Subscriber C's allocation changes from 20% (100MB) to 40% (200MB). Usage for this cycle is now recorded as 0/200, so subscriber C has 200MB left to consume this cycle. In subsequent cycles, subscriber C will continue to have a 40% allocation of the plan allotment.
Total consumption during the cycle is 210MB. There is 290MB remaining for subscribers A and C to share. Subscriber A can use up to 190MB more and subscriber C can use up to 200MB.

Allocation Change Example 3

Subscriber A was allocated 40% (200MB) and has consumed 2% (10MB).
Subscriber B was allocated 80% (400MB) and has consumed 75% (300MB).
Subscriber C was allocated 20% (100MB) and has consumed 0% (0MB).
Total consumption during the cycle: 310MB, leaving 190MB.

The account controller changes subscriber B's allocation from 80% (400MB) to 20% (100MB) and subscriber C's allocation from 20% (100MB) to 40% (200MB).

Subscriber A's allocation and remaining usage does not change.
Subscriber B's allocation changes from 80% (400MB) to 20% (100MB). Because subscriber B's current cycle usage has already exceeded the new allocation, usage for the cycle is now recorded as 100/100, and subscriber B has 0MB left to consume this cycle. In subsequent cycles, subscriber B will continue to have a 20% allocation of the plan allotment.
Subscriber C's allocation changes from 20% (100MB) to 40% (200MB). Usage for this cycle is now recorded as 10/200 because there is just 190MB left in the plan to consume. In subsequent cycles, subscriber C will continue to have a 40% allocation of the plan allotment.
Total consumption during the cycle is 310MB. There is 190MB remaining for subscribers A and C to share. Subscribers A and C combined can use up to the 190MB remaining on the plan cycle.

Subscriber Join

The new subscriber is allocated 100%.

Subscriber Unjoin

No change to allocations of remaining subscribers, except that if the number of subscribers becomes 1, the remaining subscriber's allocation changes to 100%.

Downgrade

The 500MB plan is exchanged for one with 250MB.

On systems that allow immediate downgrades (vs. downgrades being delayed until the next cycle), customers can downgrade only to plans and bundles that are at least as large as the amount consumed during the current cycle. (In the case of bundles, each plan in the bundle is considered separately.) In the above example, if total use during the cycle exceeded 250MB, a downgrade to that plan could not occur. Of if you had a bundle with 500MB data, 500 voice minutes, and 200 text messages and an exchange was desired for a bundle with 250MB data, 200 voice minutes, and 100 text messages, if data use during the cycle exceeded 250MB, voice minutes during the cycle exceeded 200 minutes, or more than 100 text messages were used, a downgrade to that bundle could not occur.

Downgrade Example 1

Before the downgrade:

Subscriber A is allocated 40% (200MB) and has consumed 2% (10MB). Usage shows 10/200.
Subscriber B is allocated 40% (200MB) and has consumed 49.5% (99MB). Usage shows 99/200.
Subscriber C is allocated 20% (100MB) and has consumed 0% (0MB). Usage shows 0/100.
Total consumption during the cycle: 109MB. Total remaining for the cycle: 391MB. Consumption has not exceeded capacity of exchanged plan, so downgrade is allowed.

After the downgrade:

Subscriber A's 40% allocation is reduced from 200MB to 100MB. Usage shows 10/100, which leaves up to 90MB.
Subscriber B's 40% allocation is reduced from 200MB to 100MB. Usage shows 99/100, which leaves up to 1MB.
Subscriber C's 20% allocation is reduced from 100MB to 50MB. Usage shows 0/50, which leaves up to 50MB.
Total consumption during the cycle: 109MB. There is now 141MB remaining for subscribers A, B, and C to share. Subscriber A can use up to 90MB more, subscriber B can use up to 1MB more, and subscriber C can use up to 50MB more.

Downgrade Example 2

Before the downgrade:

Subscriber A is allocated 40% (200MB) and has consumed 2% (10MB). Usage shows 10/200.
Subscriber B is allocated 40% (200MB) and has consumed 50.5% (101MB). Usage shows 101/200.
Subscriber C is allocated 20% (100MB) and has consumed 0% (0MB). Usage shows 0/100.
Total consumption during the cycle: 111MB. Total remaining for the cycle: 389MB. Consumption has not exceeded capacity of exchanged plan, so downgrade is allowed.

After the downgrade:

Subscriber A's 40% allocation is reduced from 200MB to 100MB. Usage shows 10/100, which leaves up to 90MB.
Subscriber B's 40% allocation is reduced from 200MB to 100MB. Usage shows 100/100 (because usage display cannot be greater than actual allocation, so the usage display indicates how much a user has remaining), which leaves 0MB.
Subscriber C's 20% allocation is reduced from 100MB to 50MB. Usage shows 0/50, which leaves up to 50MB.
Total consumption during the cycle: 111MB. There is now 139MB remaining for subscribers A and C to share. Subscriber A can use up to 90MB more and subscriber C can use up to 50MB more.

Downgrade Example 3

Before the downgrade:

Subscriber A is allocated 40% (200MB) and has consumed 2% (10MB). Usage shows 10/200.
Subscriber B is allocated 40% (200MB) and has consumed 75.5% (151MB). Usage shows 151/200.
Subscriber C is allocated 20% (100MB) and has consumed 0% (0MB). Usage shows 0/100.
Total consumption during the cycle: 161MB. Total remaining for the cycle: 339MB. Consumption has not exceeded capacity of exchanged plan, so downgrade is allowed.

After the downgrade:

Subscriber A's 40% allocation is reduced from 200MB to 100MB. Usage shows 11/100, which leaves 89MB. (While actual usage was 10MB to this point, only 89MB is available to be used, so the usage adjusts to indicate this.)
Subscriber B's 40% allocation is reduced from 200MB to 100MB. Usage shows 100/100 (because usage display cannot be greater than actual allocation, so the usage display indicates how much a user has remaining), which leaves 0MB.
Subscriber C's 20% allocation is reduced from 100MB to 50MB. Usage shows 0/50, which leaves 50MB.
Total consumption during the cycle: 161MB. There is now 89MB remaining for subscribers A and C to share. Subscriber A can use up to 89MB more and subscriber C can use up to 50MB more.

Downgrade Example 4

Before the downgrade:

Subscriber A is allocated 40% (200MB) and has consumed 2% (10MB). Usage shows 10/200.
Subscriber B is allocated 40% (200MB) and has consumed 95.5% (191MB). Usage shows 191/200.
Subscriber C is allocated 20% (100MB) and has consumed 0% (0MB). Usage shows 0/100.
Total consumption during the cycle: 201MB. Total remaining for the cycle: 49MB.

After the downgrade:

Subscriber A's 40% allocation is reduced from 200MB to 100MB. Usage shows 51/100, which leaves 49MB. (While actual usage was 10MB to this point, only 49MB is available to be used, so the usage adjusts to indicate this.)
Subscriber B's 40% allocation is reduced from 200MB to 100MB. Usage shows 100/100 (because usage display cannot be greater than actual allocation, so the usage display indicates how much a user has remaining), which leaves 0MB.
Subscriber C's 20% allocation is reduced from 100MB to 50MB. Usage shows 1/50, which leaves 49MB. (While actual usage was 0MB to this point, only 49MB is available to be used, so the usage adjusts to indicate this.)
Total consumption during the cycle: 201MB. There is now 49MB remaining for subscribers A and C to share. Subscriber A can use up to 49MB more and subscriber C can use up to 49MB more.

Upgrade

No changes to any subscriber allocation.

Share On Request: Piñata

With a Share Method setting of Manual and a Share Type setting of Piñata, this is how plan allocation behaves.

Initial Allocation

The plan or bundle purchaser receives 100% allocation. Any other subscribers in the account receive 0% initially. The purchaser/account controller can change the initial allocation from the default before completing the purchase.

Allocation Change

The account controller changes subscriber allowances.

Subscriber allowances can be changed at any time to any whole number percentage from 0% to 100%.
The total of individual allowance percentage can be greater than 100%.
If a subscriber's current cycle usage exceeds the new allowance, the subscriber will have no more usage for the current cycle.

The following examples assume you start with a 500MB data plan with 3 subscribers sharing it.

Allocation Change Example 1

Subscriber A was allocated 40% (200MB) and has consumed 2% (10MB).
Subscriber B was allocated 80% (400MB) and has consumed 19.8% (99MB).
Subscriber C was allocated 20% (100MB) and has consumed 0% (0MB).
Total consumption during the cycle: 109MB, leaving 391MB.

The account controller changes subscriber B's allocation from 80% (400MB) to 20% (100MB) and subscriber C's allocation from 20% (100MB) to 40% (200MB).

Subscriber A's allocation and remaining usage does not change.
Subscriber B's allocation changes from 80% (400MB) to 20% (100MB). Usage for the cycle is now recorded as 99/100, so subscriber B has 1MB left to consume this cycle. In subsequent cycles, subscriber B will continue to have a 20% allocation of the plan allotment.
Subscriber C's allocation changes from 20% (100MB) to 40% (200MB). Usage for this cycle is now recorded as 0/200, so subscriber C has 200MB left to consume this cycle. In subsequent cycles, subscriber C will continue to have a 40% allocation of the plan allotment.
Total consumption during the cycle: 109MB. There is 391MB remaining. Subscriber A can use up to 190MB more, subscriber B can use up to 1MB more, and subscriber C can use up to 200MB more.

Allocation Change Example 2

Subscriber A was allocated 40% (200MB) and has consumed 2% (10MB).
Subscriber B was allocated 80% (400MB) and has consumed 40% (200MB).
Subscriber C was allocated 20% (100MB) and has consumed 0% (0MB).
Total consumption during the cycle: 210MB, leaving 290MB.

The account controller changes subscriber B's allocation from 80% (400MB) to 20% (100MB) and subscriber C's allocation from 20% (100MB) to 40% (200MB).

Subscriber A's allocation and remaining usage does not change.
Subscriber B's allocation changes from 80% (400MB) to 20% (100MB). Because subscriber B's current cycle usage has already exceeded the new allocation, usage for the cycle is now recorded as 100/100, and subscriber B has 0MB left to consume this cycle. In subsequent cycles, subscriber B will continue to have a 20% allocation of the plan allotment.
Subscriber C's allocation changes from 20% (100MB) to 40% (200MB). Usage for this cycle is now recorded as 0/200, so subscriber C has 200MB left to consume this cycle. In subsequent cycles, subscriber C will continue to have a 40% allocation of the plan allotment.
Total consumption of the plan is 210MB. There is 290MB remaining. Subscriber A can use up to 190MB and subscriber B can use up to 200MB.

Allocation Change Example 3

Subscriber A was allocated 40% (200MB) and has consumed 2% (10MB).
Subscriber B was allocated 80% (400MB) and has consumed 60% (300MB).
Subscriber C was allocated 20% (100MB) and has consumed 0% (0MB).
Total plan consumption during the cycle: 310MB, leaving 190MB.

The account controller changes subscriber B's allocation from 80% (400MB) to 20% (100MB) and subscriber C's allocation from 20% (100MB) to 40% (200MB).

Subscriber A's allocation and remaining usage does not change.
Subscriber B's allocation changes from 80% (400MB) to 20% (100MB). Because subscriber B's current cycle usage has already exceeded the new allocation, usage for the cycle is now recorded as 100/100, and subscriber B has 0MB left to consume this cycle. In subsequent cycles, subscriber B will continue to have a 20% allocation of the plan allotment.
Subscriber C's allocation changes from 20% (100MB) to 40% (200MB). Usage for this cycle is now recorded as 10/200 because there is just 190MB left in the plan to consume. In subsequent cycles, subscriber C will continue to have a 40% allocation of the plan allotment.
Total consumption is 310MB. There is 190MB remaining. Subscribers A and C can use up to the 190MB remaining in the cycle.

Subscriber Join

The new subscriber is allocated 0%.

Subscriber Unjoin

No change to allocations of remaining subscribers, except that if the number of subscribers becomes 1, the remaining subscriber's allocation changes to 100%.

Downgrade

The 500MB plan is exchanged for one with 250MB.

Downgrade Example 1

Before the downgrade:

Subscriber A is allocated 40% (200MB) and has consumed 2% (10MB). Usage shows 10/200.
Subscriber B is allocated 40% (200MB) and has consumed 19.8% (99MB). Usage shows 99/200.
Subscriber C is allocated 20% (100MB) and has consumed 0% (0MB). Usage shows 0/100.
Total consumption during the cycle: 109MB. Total remaining for the cycle: 391MB. Consumption has not exceeded capacity of exchanged plan, so downgrade is allowed.

After the downgrade:

Subscriber A's 40% allocation is reduced from 200MB to 100MB. Usage shows 10/100, which leaves 90MB.
Subscriber B's 40% allocation is reduced from 200MB to 100MB. Usage shows 99/100, which leaves 1MB.
Subscriber C's 20% allocation is reduced from 100MB to 50MB. Usage shows 0/50, which leaves 50MB.
Total consumption during the cycle: 109MB. There is now 141MB remaining for subscribers A, B, and C to share. Subscriber A can use up to 90MB more, subscriber B can use up to 1MB more, and subscriber C can use up to 50MB more.

Downgrade Example 2

Before the downgrade:

Subscriber A is allocated 40% (200MB) and has consumed 2% (10MB). Usage shows 10/200.
Subscriber B is allocated 40% (200MB) and has consumed 20.2% (101MB). Usage shows 101/200.
Subscriber C is allocated 20% (100MB) and has consumed 0% (0MB). Usage shows 0/100.
Total consumption during the cycle: 111MB. Total remaining for the cycle: 389MB. Consumption has not exceeded capacity of exchanged plan, so downgrade is allowed.

After the downgrade:

Subscriber A's 40% allocation is reduced from 200MB to 100MB. Usage shows 10/100, which leaves 90MB.
Subscriber B's 40% allocation is reduced from 200MB to 100MB. Usage shows 100/100 (because usage display cannot be greater than actual allocation, so the usage display indicates how much a user has remaining), which leaves 0MB.
Subscriber C's 20% allocation is reduced from 100MB to 50MB. Usage shows 0/50, which leaves 50MB.
Total consumption during the cycle: 111MB. There is now 139MB remaining for subscribers A, B, and C to share. Subscriber A can use up to 90MB more, subscriber B can use up to 1MB more, and subscriber C can use up to 50MB more.

Downgrade Example 3

Before the downgrade:

Subscriber A is allocated 40% (200MB) and has consumed 2% (10MB). Usage shows 10/200.
Subscriber B is allocated 40% (200MB) and has consumed 30.2% (151MB). Usage shows 151/200.
Subscriber C is allocated 20% (100MB) and has consumed 0% (0MB). Usage shows 0/100.
Total consumption during the cycle: 161MB. Total remaining for the cycle: 339MB. Consumption has not exceeded capacity of exchanged plan, so downgrade is allowed.

After the downgrade:

Subscriber A's 40% allocation is reduced from 200MB to 100MB. Usage shows 11/100, which leaves 89MB. (While actual usage was 10MB to this point, only 89MB is available to be used, so the usage adjusts to indicate this.)
Subscriber B's 40% allocation is reduced from 200MB to 100MB. Usage shows 100/100 (because usage display cannot be greater than actual allocation, so the usage display indicates how much a user has remaining), which leaves 0MB.
Subscriber C's 20% allocation is reduced from 100MB to 50MB. Usage shows 0/50, which leaves 50MB.
Total consumption during the cycle: 161MB. There is now 89MB remaining for subscribers A and C to share. Subscriber A can use up to 89MB more and subscriber C can use up to 50MB more.

Downgrade Example 4

Before the downgrade:

Subscriber A is allocated 40% (200MB) and has consumed 2% (10MB). Usage shows 10/200.
Subscriber B is allocated 40% (200MB) and has consumed 38.2% (191MB). Usage shows 191/200.
Subscriber C is allocated 20% (100MB) and has consumed 0% (0MB). Usage shows 0/100.
Total consumption during the cycle: 201MB. Total remaining for the cycle: 299MB. Consumption has not exceeded capacity of exchanged plan, so downgrade is allowed.

After the downgrade:

Subscriber A's 40% allocation is reduced from 200MB to 100MB. Usage shows 51/100, which leaves 49MB. (While actual usage was 10MB to this point, only 49MB is available to be used, so the usage adjusts to indicate this.)
Subscriber B's 40% allocation is reduced from 200MB to 100MB. Usage shows 100/100 (because usage display cannot be greater than actual allocation, so the usage display indicates how much a user has remaining), which leaves 0MB.
Subscriber C's 20% allocation is reduced from 100MB to 50MB. Usage shows 1/50, which leaves 49MB. (While actual usage was 0MB to this point, only 49MB is available to be used, so the usage adjusts to indicate this.)
Total consumption during the cycle: 201MB. There is now 49MB remaining for subscribers A and C to share. Subscriber A can use up to 49MB more and subscriber C can use up to 49MB more.

Upgrade

No changes to any subscriber allocation.

Share Automatically: Limited

With a Share Method setting of Automatic and a Share Type setting of Limited, this is how allocation behaves.

Initial Allocation

Each subscriber in the account gets allocated an equal amount. The purchaser/account controller can change the initial allocation from the default before completing the purchase.

Allocation Change

The account controller changes subscriber allowances.

Subscriber allowances can be changed at any time to any whole number percentage from 0% to 100%.
A subscriber allowance cannot be changed to lower than what the subscriber has already used.
A subscriber allowance cannot be changed to higher than the remaining available plan usage.
The total of individual allowance percentage cannot be greater than 100%.

The following examples assume you start with a 500MB data plan with 3 subscribers sharing it.

Allocation Change Example 1

Subscriber A was allocated 40% (200MB) and has consumed 2% (10MB).
Subscriber B was allocated 40% (200MB) and has consumed 19.8% (99MB).
Subscriber C was allocated 20% (100MB) and has consumed 0% (0MB).
Total consumption during the cycle: 109MB, leaving 391MB.

Subscriber A cannot be reallocated to less than 2% and Subscriber B cannot be reallocated to less than 20%. No subscriber can have their allocation changed to more than what they have used plus the remaining plan allocation, which means:

Subscriber A's allocation cannot be increased to more than 80%.
Subscriber B's allocation cannot be increased to more than 97%.
Subscriber C's allocation cannot be increased to more than 78%.

The account controller changes subscriber A's allocation from 40% (200MB) to 50% (250MB) and subscriber B's allocation from 40% (200MB) to 20% (100MB).

Subscriber A's allocation changes from 40% (200MB) to 50% (250MB). Usage for the cycle is now recorded as 10/250, so subscriber A has 240MB left to consume this cycle. In subsequent cycles, subscriber A will continue to have a 50% allocation of the plan allotment.
Subscriber B's allocation changes from 40% (200MB) to 20% (100MB). Usage for the cycle is now recorded as 99/100, so subscriber B has 1MB left to consume this cycle. In subsequent cycles, subscriber B will continue to have a 20% allocation of the plan allotment.
Subscriber C's allocation and remaining usage does not change.
There is 10% (50MB) unallocated.

Allocation Change Example 2

Subscriber A was allocated 40% (200MB) and has consumed 22% (110MB).
Subscriber B was allocated 40% (200MB) and has consumed 40% (200MB).
Subscriber C was allocated 20% (100MB) and has consumed 0% (0MB).
Total consumption during the cycle: 310MB, leaving 190MB.

Subscriber A cannot be reallocated to less than 22% and Subscriber B cannot be reallocated to less than 40%. No subscriber can have their allocation changed to more than what they have used plus the remaining plan allocation, which means:

Subscriber A's allocation cannot be increased to more than 60%.
Subscriber B's allocation cannot be increased to more than 78%.
Subscriber C's allocation cannot be increased to more than 38%.

The account controller changes subscriber A's allocation from 40% (200MB) to 60% (300MB).

Subscriber A's allocation changes from 40% (200MB) to 60% (300MB). Usage for the cycle is now recorded as 200/300, so subscriber A has 100MB left to consume this cycle. In subsequent cycles, subscriber A will continue to have a 60% allocation of the plan allotment.
Subscriber B's allocation and remaining usage does not change. Usage for the cycle is recorded as 200/200, so subscriber B has 0MB left to consume this cycle.
Subscriber C's allocation is reduced to 0% (0MB). Usage for the cycle is now recorded as 0/0. In subsequent cycles, subscriber C will continue to have 0% of the plan allotment.

Allocation Change Example 3

Subscriber A was allocated 40% (200MB) and has consumed 22% (110MB).
Subscriber B was allocated 40% (200MB) and has consumed 30% (150MB).
Subscriber C was allocated 20% (100MB) and has consumed 2% (10MB).
Total consumption during the cycle: 270MB, leaving 230MB.

Subscriber A cannot be reallocated to less than 22%, Subscriber B cannot be reallocated to less than 30%, and Subscriber C cannot be reallocated to less than 2%. No subscriber can have their allocation changed to more than what they have used plus the remaining plan allocation, which means:

Subscriber A's allocation cannot be increased to more than 68%.
Subscriber B's allocation cannot be increased to more than 76%.
Subscriber C's allocation cannot be increased to more than 48%.

The account controller changes subscriber A's allocation from 40% (200MB) to 50% (250MB).

Subscriber A's allocation changes from 40% (200MB) to 50% (250MB). Usage for the cycle is now recorded as 110/250, so subscriber A has 140MB left to consume this cycle. In subsequent cycles, subscriber A will continue to have a 50% allocation.
Subscriber B's allocation and remaining usage does not change. Usage for the cycle is recorded as 150/200, so subscriber B has 50MB left to consume this cycle.
Subscriber C's allocation is reduced to 10% (50MB). Usage for the cycle is now recorded as 10/50, so Subscriber C has 40MB left to consume this cycle. In subsequent cycles, subscriber C will continue to have a 10% allocation.

Subscriber Join

If there is an unallocated amount, 100% of that is allocated to the new subscriber. If there is no unallocated amount, the new subscriber is allocated 0%.

Subscriber Unjoin

No change to allocations of remaining subscribers, except that if the number of subscribers becomes 1, the remaining subscriber's allocation changes to 100%.

Downgrade

For downgrades, the following rules apply:

If no subscribers have exceeded their new allowances, there are no changes to allocations.
If at any subscribers have exceeded their new allowance, those subscribers have a new allowance calculated as their current cycle use divided by the new allowance. Any remaining allocation is divided among other subscribers proportional to their existing allowance.
If after the above adjustments, any other subscribers have exceeded their new allowance, their usage for the cycle is capped at that amount. Any remaining allocation is shared among subscribers not adjusted as above.

The 500MB plan is exchanged for one with 250MB.

Downgrade Example 1

Before the downgrade:

Subscriber A is allocated 40% (200MB) and has consumed 2% (10MB). Usage shows 10/200.
Subscriber B is allocated 40% (200MB) and has consumed 19.8% (99MB). Usage shows 99/200.
Subscriber C is allocated 20% (100MB) and has consumed 0% (0MB). Usage shows 0/100.
Total consumption during the cycle: 109MB. Total remaining for the cycle: 391MB.

After the downgrade:

Total allotment remaining for the cycle: 141MB.
Subscriber A's 40% allocation is reduced from 200MB to 100MB. Usage shows 10/100, which leaves 90MB.
Subscriber B's 40% allocation is reduced from 200MB to 100MB. Usage shows 99/100, which leaves 1MB.
Subscriber C's 20% allocation is reduced from 100MB to 50MB. Usage shows 0/50, which leaves 50MB.

Downgrade Example 2

Before the downgrade:

Subscriber A is allocated 40% (200MB) and has consumed 4% (20MB). Usage shows 20/200.
Subscriber B is allocated 40% (200MB) and has consumed 22.2% (111MB). Usage shows 111/200.
Subscriber C is allocated 20% (100MB) and has consumed 0% (0MB). Usage shows 0/100.
Total consumption during the cycle: 131MB. Total remaining for the cycle: 369MB.

After the downgrade:

Total allotment remaining for the cycle: 119MB.
Subscriber A had 2/3 of the allocation of subscriber A and subscriber C combined (40 / (40 + 20)). Subscriber A now gets 2/3 of the remaining allocation of 56%, or 37.3%, which is rounded to 37%. Subscriber A's 40% allocation is reduced to 37%, from 200MB to 92.5MB. Usage shows 10/92.5, which leaves 82.5MB.
Subscriber B has used more than the 40% of 100MB, so the allocation percentage changes to equal usage. Subscriber B's 40% allocation percentage is changed to 44.4% (111 of 250), which is rounded to 44% leaving 56% for the rest of the subscribers, and allocation is reduced from 200MB to 111MB. Usage shows 111/111, which leaves 0MB.
Subscriber C had 1/3 of the allocation of subscriber A and subscriber C combined (20 / (40 + 20)). Subscriber C now gets 1/3 of the remaining allocation of 56%, or 18.7%, which is rounded to 19%. Subscriber C's 20% allocation is reduced to 19%, from 100MB to 47.5MB. Usage shows 0/47.5, which leaves 47.5MB.

Downgrade Example 3

Before the downgrade:

Subscriber A is allocated 40% (200MB) and has consumed 2% (10MB). Usage shows 10/200.
Subscriber B is allocated 40% (200MB) and has consumed 40% (200MB). Usage shows 200/200.
Subscriber C is allocated 20% (100MB) and has consumed 0% (0MB). Usage shows 0/100.
Total consumption during the cycle: 210MB. Total remaining for the cycle: 290MB.

After the downgrade:

Total allotment remaining for the cycle: 40MB.
Subscriber A had 2/3 of the allocation of subscriber A and subscriber C combined (40 / (40 + 20)). Subscriber A now gets 2/3 of the remaining allocation of 20% (what's left after subscriber B's adjustment), or 13.3%, which is rounded to 13%. Subscriber A's 40% allocation is reduced to 13%, from 200MB to 32.5MB. Usage shows 10/32.5, which leaves 22.5MB.
Subscriber B has used more than the 40% of 100MB, so the allocation percentage changes to equal usage. Subscriber B's 40% allocation percentage is changed to 80% (200 of 250), leaving 20% for the rest of the subscribers. Allocation remains at 200MB. Usage shows 200/200, which leaves 0MB.
Subscriber C had 1/3 of the allocation of subscriber A and subscriber C combined (20 / (40 + 20)). Subscriber C now gets 1/3 of the remaining allocation of 20% (what's left after subscriber B's adjustment), or 6.7%, which is rounded to 7%. Subscriber C's 20% allocation is reduced to 7%, from 100MB to 17.5MB. Usage shows 0/17.5, which leaves 17.5MB.

Downgrade Example 4

Before the downgrade:

Subscriber A is allocated 40% (200MB) and has consumed 2% (10MB). Usage shows 10/200.
Subscriber B is allocated 40% (200MB) and has consumed 40% (200MB). Usage shows 200/200.
Subscriber C is allocated 20% (100MB) and has consumed 4% (20MB). Usage shows 20/100.
Total consumption during the cycle: 230MB. Total remaining for the cycle: 270MB.

After the downgrade:

Total allotment remaining for the cycle: 20MB.
Subscriber A had 2/3 of the allocation of subscriber A and subscriber C combined (40 / (40 + 20)). Subscriber A now gets 2/3 of the remaining allocation of 20%, or 13.3%, which is rounded to 13% and is 32.5MB. But after subscriber B's usage and subscriber C's usage, there is only 20MB left to consume. 20MB is 8%, so while subscriber A's 40% allocation is reduced from 200MB to 32.5MB, Usage shows 12.5/32.5, reflecting the 20MB remaining to be used in the cycle.
Subscriber B has used more than the 40% of 100MB, so the allocation percentage changes to equal usage. Subscriber B's 40% allocation percentage is changed to 80% (200 of 250), leaving 20% for the rest of the subscribers. Allocation remains at 200MB. Usage shows 200/200, which leaves 0MB.
Subscriber C had 1/3 of the allocation of subscriber A and subscriber C combined (20 / (40 + 20)). Subscriber C now gets 1/3 of the remaining allocation of 20%, or 6.7%, which is rounded to 7% and is 17.5MB. But subscriber C has already used 20MB, which is 8% of 250MB. So Subscriber C's 20% allocation is changed to 8%, not 7%, from 100MB to 20MB. Usage shows 20/20, which leaves 0MB.

Upgrade

No changes to any subscriber allocation.

Share On Request: Limited

With a Share Method setting of Manual and a Share Type setting of Limited, this is how allocation behaves.

Initial Allocation

The purchaser receives 100% allocation. Any other subscribers in the account receive 0% initially.

Allocation Change

The account controller changes subscriber allowances.

Subscriber allowances can be changed at any time to any whole number percentage from 0% to 100%.
A subscriber allowance cannot be changed to lower than what the subscriber has already used.
A subscriber allowance cannot be changed to higher than the remaining available plan usage.
The total of individual allowance percentage cannot be greater than 100%.

The following examples assume you start with a 500MB data plan with 3 subscribers sharing it.

Allocation Change Example 1

Subscriber A was allocated 40% (200MB) and has consumed 2% (10MB).
Subscriber B was allocated 40% (200MB) and has consumed 19.8% (99MB).
Subscriber C was allocated 20% (100MB) and has consumed 0% (0MB).
Total consumption during the cycle: 109MB (21.8%), leaving 391MB (78.2%).

Subscriber A's allocation cannot be increased to more than 80%.
Subscriber B's allocation cannot be increased to more than 97%.
Subscriber C's allocation cannot be increased to more than 78%.

The account controller changes subscriber A's allocation from 40% (200MB) to 50% (250MB) and subscriber B's allocation from 40% (200MB) to 20% (100MB).

Subscriber A's allocation changes from 40% (200MB) to 50% (250MB). Usage for the cycle is now recorded as 10/250, so subscriber A has 240MB left to consume this cycle. In subsequent cycles, subscriber A will continue to have a 50% allocation of the allotment.
Subscriber B's allocation changes from 40% (200MB) to 20% (100MB). Usage for the cycle is now recorded as 99/100, so subscriber B has 1MB left to consume this cycle. In subsequent cycles, subscriber B will continue to have a 20% allocation of the allotment.
Subscriber C's allocation and remaining usage does not change.
There is 10% (50MB) unallocated.

Allocation Change Example 2

Subscriber A was allocated 40% (200MB) and has consumed 22% (110MB).
Subscriber B was allocated 40% (200MB) and has consumed 100% (200MB).
Subscriber C was allocated 20% (100MB) and has consumed 0% (0MB).
Total consumption during the cycle: 310MB (62%), leaving 190MB (38%).

Subscriber A's allocation cannot be increased to more than 60%.
Subscriber B's allocation cannot be increased to more than 78%.
Subscriber C's allocation cannot be increased to more than 38%.

The account controller changes subscriber A's allocation from 40% (200MB) to 60% (300MB).

Subscriber A's allocation changes from 40% (200MB) to 60% (300MB). Usage for the cycle is now recorded as 200/300, so subscriber A has 100MB left to consume this cycle. In subsequent cycles, subscriber A will continue to have a 60% allocation of the allotment.
Subscriber B's allocation and remaining usage does not change. Usage for the cycle is recorded as 200/200, so subscriber B has 0MB left to consume this cycle.
Subscriber C's allocation is reduced to 0% (0MB). Usage for the cycle is now recorded as 0/0. In subsequent cycles, subscriber C will continue to have 0% of the allotment.

Allocation Change Example 3

Subscriber A was allocated 40% (200MB) and has consumed 22% (110MB).
Subscriber B was allocated 40% (200MB) and has consumed 30% (150MB).
Subscriber C was allocated 20% (100MB) and has consumed 2% (10MB).
Total consumption during the cycle: 270MB (54%), leaving 230MB (46%).

Subscriber A's allocation cannot be increased to more than 68%.
Subscriber B's allocation cannot be increased to more than 76%.
Subscriber C's allocation cannot be increased to more than 48%.

The account controller changes subscriber A's allocation from 40% (200MB) to 50% (250MB).

Subscriber A's allocation changes from 40% (200MB) to 50% (250MB). Usage for the cycle is now recorded as 110/250, so subscriber A has 140MB left to consume this cycle. In subsequent cycles, subscriber A will continue to have a 50% allocation of the allotment.
Subscriber B's allocation and remaining usage does not change. Usage for the cycle is recorded as 150/200, so subscriber B has 50MB left to consume this cycle.
Subscriber C's allocation is reduced to 10% (50MB). Usage for the cycle is now recorded as 10/50, so Subscriber C has 40MB left to consume this cycle. In subsequent cycles, subscriber C will continue to have 10% of the allotment.

Subscriber Join

The new subscriber is allocated 0%.

Subscriber Unjoin

No change to allocations of remaining subscribers, except that if the number of subscribers becomes 1, the remaining subscriber's allocation changes to 100%.

Plan Downgrade

Upon completion of downgrade, account controller is taken to the Change Allowances page. No automatic reallocation occurs.

Plan Upgrade

Upon completion of upgrade, account controller is taken to the Change Allowances page. No automatic reallocation occurs.