Skip to content
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.

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

Phase 2: Split Between Premium and Enterprise Tiers #2329

Closed
2 tasks done
Tracked by #2167
MarianRaphael opened this issue Jun 22, 2023 · 0 comments
Closed
2 tasks done
Tracked by #2167

Phase 2: Split Between Premium and Enterprise Tiers #2329

MarianRaphael opened this issue Jun 22, 2023 · 0 comments
Labels
epic A significant feature or piece of work that doesn't easily fit into a single release headline Something to highlight in the release priority:high High Priority

Comments

@MarianRaphael
Copy link
Contributor

MarianRaphael commented Jun 22, 2023

Description

The focus of Phase 2 is to differentiate between the Premium and Enterprise tiers in the FlowForge offering.

Similar to the Premium tier, the Enterprise tier will also have an SLA for support and availability of the FlowForge platform. However, we plan to introduce an 'Organization hierarchy' as an exclusive feature of the Enterprise tier. This feature will provide more control and flexibility for larger organizations in managing their FlowForge instances and teams.

Packaging details: Google Docs

Tasks

  1. 3 of 3
    priority:high size:M - 3
    knolleary
  2. 4 of 4
    priority:high size:XL - 8
    hardillb
@MarianRaphael MarianRaphael added the epic A significant feature or piece of work that doesn't easily fit into a single release label Jun 22, 2023
@MarianRaphael MarianRaphael added the headline Something to highlight in the release label Aug 26, 2023
@MarianRaphael MarianRaphael added the priority:high High Priority label Aug 31, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
epic A significant feature or piece of work that doesn't easily fit into a single release headline Something to highlight in the release priority:high High Priority
Projects
Archived in project
Archived in project
Development

No branches or pull requests

2 participants