Roles

Team roles determine who can manage the team and the billing relationship. Source and lockfile actions are available to everyone.

Action	Owner	Admin	Member
View sources, lockfiles, alerts	✓	✓	✓
Add / remove sources	✓	✓	✓
Upload / replace lockfiles	✓	✓	✓
Acknowledge alerts	✓	✓	✓
Invite members	✓	✓	–
Remove members	✓	✓	–
Change member roles	✓	✓	–
Manage billing / add or remove seats	✓	–	–
Transfer ownership	✓	–	–
Delete the team	✓	–	–

Notes on the matrix #

• One owner per team. The owner is whoever set up the team. Ownership transfers via the team page (see Transferring ownership).
• Admins are operationally equivalent to owners for member management; they just can't change billing or remove the team.
• Members can see and modify content (sources, lockfiles), which is the point. The role distinction is purely about administrative actions.

Promoting and demoting #

From the team page, click a member's row → Change role. Owners can promote and demote anyone. Admins can promote members to admin or demote other admins to member, but can't demote the owner.

Transferring ownership #

Only the owner can hand the team over, and only to an admin: promote a member first if you need to. On the team page, click Transfer Ownership on their row. What happens next depends on whether the team's subscription still renews.

• No renewing subscription (a free team, or one whose subscription has been cancelled): ownership moves at once.

• A renewing subscription: our payment provider can't move a subscription to someone else's card, and nobody is charged without agreeing to it. So the new owner takes over by checking out with their own card for the Team plan, on the team's current billing interval. Until they have:

  • ownership and billing stay with you, and nothing changes for the team;
  • the team page shows the pending handover to the two of you, and to nobody else, and either of you can cancel it there;
  • the handover lapses after 7 days if they haven't paid by then;
  • the plan and the seat count can't be changed, so the checkout stays priced for the team as it is.

  When their payment goes through, their subscription becomes the team's, they become the owner, and your subscription is cancelled at our payment provider, all at once. You get back the unused part of your current billing period, pro rata (see Refunds), and you stay on the team as an admin. Nobody pays twice for the same days, and the team is never without a plan.

A few things follow from that:

• The new owner's checkout starts a subscription of their own, so it comes with its own 14-day right of withdrawal.
• If the admin a handover is waiting for leaves the team, is removed, is made a member again, or deletes their account, the handover is cancelled.
• A payment that can't complete the handover makes nobody the owner: that subscription is ended and the payment refunded in full. That covers a handover that was cancelled or had lapsed before the payment, and a payment that isn't the new owner's own checkout for this handover, or is for another plan or billing interval. A payment of the second kind leaves the handover as it was, so the new owner can still check out.
• The new owner can open the checkout more than once (in another tab, say); whichever one they pay completes the handover.
• A paid team with more than the 5 seats the base plan includes can't be handed over from the team page yet, because the new owner's checkout covers the base plan. Write to info@devupdate.io and we'll arrange it.
• Nor can a paid team whose current owner's refund we can't work out from the payments we hold. The team page says which of these applies, and in each case info@devupdate.io arranges the handover instead:
  • The plan changed during the current billing period (Professional to Team, or a new billing interval). That change is charged as a payment of its own, and how your refund would split between it and the period's first payment can't be worked out until the subscription has renewed; after that the team page works again.
  • We hold no record of the payment for the current period, as for a subscription older than our payment records.
  • The last payment was for a product we don't recognise.
• If the plan changes while a handover is pending anyway, the handover still completes and the current owner's subscription is still cancelled, but their refund is worked out and issued by us by hand rather than guessed, which can take a few business days (write to info@devupdate.io with any question).

Leaving a team #

Members leave the team from their own settings. Owners can't leave; they must first transfer ownership to an admin. Once you leave, you lose visibility into team-scoped sources and lockfiles, but your individual account is preserved.