Enforce Organization Validity Period #384
Labels
No labels
API
Billing
UI/UX
dependencies
bug
change
duplicate
enhancement
help wanted
invalid
question
wontfix
No milestone
No project
No assignees
2 participants
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
servala/servala-portal#384
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Stories
As a platform owner, I want to enforce the validity period of an organization
Implementation Notes
In #380 we allow configuring "Organization validity in number of days from the date of creation". We actually need to enforce this.
When an organization has passed the validity period configured in organization limits, "lock" the organization from doing create and update operations. Read-only access is still allowed, as well as creating support requests.
To make the user aware of the fact that the organization has a validity period:
Note: Stopping or removing instances is out of the scope of this issue.
What is the call-to-action with the limited validity period? Both the emails and the frontend message should have some sort of call to action to get past the limit, right?
Yes, that's true. For now, the CTA isn't very attractive, but that's currently all we have: "Contact us to raise your limits" or something along that line.
Should we always show the banner with the expiry information, or only e.g. in the 14 (or 30) days before the expiry date?
Yes