Skip to content

Enterprise account dormancy #8128

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom
Closed
ammario opened this issue Jun 21, 2023 · 4 comments
Closed

Enterprise account dormancy #8128

ammario opened this issue Jun 21, 2023 · 4 comments
Assignees
@mtojek
Labels
enterprise Enterprise-license / premium functionality must-do Issues that must be completed by the end of the Sprint. Or else. Only humans may set this.

Comments

@ammario
Copy link
Member

ammario commented Jun 21, 2023 •
edited
Loading

In v1 we had a feature called account dormancy which marked users as "dormant" after they had been inactive for 90 days. The mark was automatically removed once the user was seen again, so it did not suspend the user.

This behavior is nearly exactly what's employed by GitHub Enterprise and GitLab, so we should bring it here too.

Automatic Provisioning

Automatic provisioning systems (e.g. SCIM) can create lots of unused user accounts. We want to encourage our customers to use these systems and make it easy for new groups to try Coder. Thus, we should mark these automatically provisioned accounts as dormant until first login.
@ammario ammario added feature enterprise Enterprise-license / premium functionality must-do Issues that must be completed by the end of the Sprint. Or else. Only humans may set this. labels Jun 21, 2023
@ammario ammario added this to the ❓Sprint 2 milestone Jun 21, 2023
@ammario ammario removed this from the ❓Sprint 2 milestone Jun 29, 2023
@bpmct
Copy link
Member

bpmct commented Jul 17, 2023 •
edited
Loading

Yep, we'll need to add a dormant state to users which occur in these scenarios:

  • When the user account is created, but has never logged in (e.g. with SCIM)
  • When the user hasn't performed an action in Coder in over 90 days

Other requirements

  • Admins should be able to manually set accounts as "dormant"
  • Dormant users should not be counted against an enterprise license.

What about suspended?

We probably want to avoid using this state for dormancy since it prevents users from logging back in. They would have to contact a Coder admin to regain access to their account.

@mtojek mtojek self-assigned this Jul 20, 2023
@mtojek
Copy link
Member

mtojek commented Jul 20, 2023

It looks like this issue is next in line, so I'm taking it.

@mtojek
Copy link
Member

mtojek commented Jul 20, 2023 •
edited
Loading

Battle plan:

  • Configure a periodic job to mark inactive accounts (90 days) as dormant

My main question is whether we can use user_state (active - dormant - suspende), or maybe we should introduce another bool column dormant. I have not identified any blockers against the first option, and "dormant" seems to be contrary to "active" any way.

@mtojek mtojek mentioned this issue Jul 21, 2023
Merged
@mtojek
Copy link
Member

mtojek commented Aug 2, 2023

Resolved in #8644

@mtojek mtojek closed this as completed Aug 2, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@mtojek mtojek

Labels
enterprise Enterprise-license / premium functionality must-do Issues that must be completed by the end of the Sprint. Or else. Only humans may set this.
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
3 participants
@ammario @mtojek @bpmct