# Summary Should be able to perform tasks to alter the namespace, replacing existing mechanizer functionality. These controls should be available to users with admin role on customersdot. Trial extension functionality [was built in gitlab.com](https://gitlab.com/groups/gitlab-org/-/epics/5776 "Empower users by creating in-app (SaaS) trial controls MVC"), but was switched off in production and never used. We should review the work done in https://gitlab.com/groups/gitlab-org/-/epics/5776+ and see if we can reuse or copy any of the logic from this past work, if we feel this work would be useful or help save time. If we're not able to reuse the work, we can build it new. ### Iterations: 1. [Namespace lookup in customersdot](https://gitlab.com/gitlab-org/customers-gitlab-com/-/issues/5524 "[MVC] Namespace lookup in customersdot") 2. [Change trial plan](https://gitlab.com/gitlab-org/customers-gitlab-com/-/issues/5310 "Allow cdot admin to change a trial plan on a namespace") 3. [Extend the end date of a trial](https://gitlab.com/gitlab-org/customers-gitlab-com/-/issues/5311 "Allow cdot admin to change trial dates on a namespace") 4. [Set NFR trial](https://gitlab.com/gitlab-org/customers-gitlab-com/-/issues/5527 "Allow cdot admin to set NFR details") # Prioritization and ROI #### Why is this feature set important Creating controls for trials in Customersdot allows us to deprecate the use of these functions in Mechanizer. Deprecating the use of Mechanizer functions means: 1. Reduced maintenance burden on the support team 2. Reduced pipeline minutes cost (every time a mechanizer function is used, a pipeline is run) 3. Reduced namespaces in abnormal state (more likely for namespace to get into abnormal state when Mechanizer is used) 4. Reduced errors and need for complex troubleshooting because of nr. 3 --- **Support Priority Score:** 15