De-couple ownership from seat allocation

[kcochran-contessa]

Tell us about your request I would like the ability to manage an organization and its team members without consuming a seat on that team.

Which service(s) is this request for? Docker Desktop

Tell us about the problem you're trying to solve. What are you trying to do, and why is it hard? Currently, I cannot manage/allocate seats for my team without that also consuming a license.

Are you currently working around the issue? As a workaround, I must and so I must designate a team member as owner and not have visibility or management access to that team.

Additional context In most larger organizations, the leadership and the hands-on-keyboard development are separated duties (meaning not with the same people). I don't need a seat for Docker Desktop, but I do need the ability to manage all the seats that I purchased for my team.

[francesco-corti]

Hi Kevin,

Yes, what you describe makes sense and we have it in our radar.

To be more precise we are already working on it as part of a broader initiative to make our entitlement/subscription solution more powerful and enhanced.

I can imagine that your next question could be: when will it be ready for us?

Two things:

• The topic is still under the design phase (but we are confident it will be prioritised and finalised pretty soon).
• Release dates are not clear yet, but we want this to be ready within the summer (if the plan will be confirmed).

Let's sync again on this topic in some weeks (middle of April?) so that we can track the progress on our side.

In the meantime let me know if we can do anything to clarify and help.

Thanks.

[kcochran-contessa]

Hi Kevin,

Yes, what you describe makes sense and we have it in our radar.

To be more precise we are already working on it as part of a broader initiative to make our entitlement/subscription solution more powerful and enhanced.

I can imagine that your next question could be: when will it be ready for us?

Two things:

• The topic is still under the design phase (but we are confident it will be prioritised and finalised pretty soon).
• Release dates are not clear yet, but we want this to be ready within the summer (if the plan will be confirmed).

Let's sync again on this topic in some weeks (middle of April?) so that we can track the progress on our side.

In the meantime let me know if we can do anything to clarify and help.

Thanks.

@francesco-corti Greetings! Just checking back in to see if you have any update on this. Thanks!

[francesco-corti]

Greetings @kcochran-contessa,

Yes, good news. This is currently planned to be developed but it will require some time because it implies the rework of a core component of the entitlement (something that we are doing).

The plan is saying that in June/July we should be fine.

Let's sync around that timeframe for a better update, if it works for you.

[kcochran-contessa]

Greetings @kcochran-contessa,

Yes, good news. This is currently planned to be developed but it will require some time because it implies the rework of a core component of the entitlement (something that we are doing).

The plan is saying that in June/July we should be fine.

Let's sync around that timeframe for a better update, if it works for you.

Great! Thank you for the update.

[kcochran-contessa]

@francesco-corti Hello! I'm checking back on this issue to get a current status now that we're past the midway point of June. Thanks

[francesco-corti]

Hi @kcochran-contessa, Thank you for checking. I confirm the feature as part of the roadmap, but because of higher priorities on other enhancements, this one won't happen before October (for the moment). We can check at that time, if it's ok for you. Thank you for your patience (and, again, for checking).

[kcochran-contessa]

@francesco-corti Wow! That's a long way out to push it when it was mentioned as a June/July target back in April. Any chance to pull it in sooner than October?

[francesco-corti]

I hear you but since then two things happened: we had to move ahead the work related to the entitlement (something that is on track) and there are other company priorities impacting this feature in this period. I confirm that is in our backlog and we know it is important for our customers. Happy to provide updates (maybe around October). I'm sorry if this causing problems (if this is the case I suggest to get in touch with our Customer Success or myself, for mitigation actions).

[kcochran-contessa]

@francesco-corti I'm checking in to see how this is looking for October. If it is more likely to continue to get pushed out, is there an alternative option that can be explored like a "license 0" or a "license + 1"? e.g. Perhaps purchasing 8 seats should actually grant 9 seats until this user story can be prioritized so that I can effectively manage my team.

[francesco-corti]

Hi @kcochran-contessa, Sorry for the delay in reply, but I was asking internally for some clarifications (trying to provide you with the best support, of course). Yes, as you guess the milestone has been moved again due to other priorities. I know it is not ideal, but we still have this in our roadmap. To your request of "workaround", the company owner doesn't occupy a seat so you can leverage this. If you are not a business subscriber, you cannot create a company layer and the problem is still there. I recommend to get in touch with our support for further details or discussions about your specific use case. Of course let me know if I can help.