# Add a screen for Tulip account owner to have visibility of available/enabled feature flags

**URL:** <https://community.tulip.co/t/add-a-screen-for-tulip-account-owner-to-have-visibility-of-available-enabled-feature-flags/11560>\
**Category:** Product Suggestions\
**Created:** [May 24, 2024, 11:15am UTC](https://community.tulip.co/t/add-a-screen-for-tulip-account-owner-to-have-visibility-of-available-enabled-feature-flags/11560 "2024-05-24T11:15:49Z")\
**Posts on this page:** 15\
**Page:** 1

<div class="post-metadata">

**Author:** ![sebme](https://avatars.discourse-cdn.com/v4/letter/s/439d5e/32.png) [@sebme](https://community.tulip.co/u/sebme)\
**Post date:** [May 24, 2024, 11:15am UTC](https://community.tulip.co/t/add-a-screen-for-tulip-account-owner-to-have-visibility-of-available-enabled-feature-flags/11560/1 "2024-05-24T11:15:49Z")

</div>

Tulip seems to have a lot of hidden “feature flags” that enable/disable functionality on one’s instance. It would be very nice to have transparency over what there is, and whether it is enabled or not without always having to go through support.

---

<div class="post-metadata">

**Author:** ![Grant](https://sea2.discourse-cdn.com/flex020/user_avatar/community.tulip.co/grant/32/182_2.png) [@Grant](https://community.tulip.co/u/Grant)\
**Post date:** [May 24, 2024, 5:38pm UTC](https://community.tulip.co/t/add-a-screen-for-tulip-account-owner-to-have-visibility-of-available-enabled-feature-flags/11560/2 "2024-05-24T17:38:36Z")

</div>

Hi @sebme,

We appreciate the product suggestion and are actively working on initiatives to provide more transparency in the configuration of instances. We want to ensure that customers have full visibility into their config so that instances perform predictably.

I’ll make sure to keep this thread updated as these efforts progress. We’re also working to substantially pair down this list of flags and provide more control direct to users, for example:

> [@Release 278 - April 2024](https://community.tulip.co/t/release-278-april-2024/11352/4):
>
> Hi @Nicolas and @danielpomeranz , two things for clarification: We pulled this feature from this release due to bugs that we could not squash in time. It should be in the next release, 279. The functionality is strictly for customers that use SAML. It allows you to control at the account level whether operators are able to log into the Player via SAML credentials or badge ID. So, it is existing functionality that was previously only available to Tulip support team members, that will now be ava…

---

<div class="post-metadata">

**Author:** ![fti](https://avatars.discourse-cdn.com/v4/letter/f/fbc32d/32.png) [@fti](https://community.tulip.co/u/fti)\
**Post date:** [February 25, 2025, 4:01pm UTC](https://community.tulip.co/t/add-a-screen-for-tulip-account-owner-to-have-visibility-of-available-enabled-feature-flags/11560/3 "2025-02-25T16:01:53Z")

</div>

@sebme This would be helpful, especially for partners (who work with multiple instances).

---

<div class="post-metadata">

**Author:** ![kevin.kononenko](https://sea2.discourse-cdn.com/flex020/user_avatar/community.tulip.co/kevin.kononenko/32/32_2.png) [@kevin.kononenko](https://community.tulip.co/u/kevin.kononenko)\
**Post date:** [February 25, 2025, 4:22pm UTC](https://community.tulip.co/t/add-a-screen-for-tulip-account-owner-to-have-visibility-of-available-enabled-feature-flags/11560/4 "2025-02-25T16:22:49Z")

</div>

Hello Fabien, are you currently able to view the IQ certificates for each of your customer instances?

---

<div class="post-metadata">

**Author:** ![fti](https://avatars.discourse-cdn.com/v4/letter/f/fbc32d/32.png) [@fti](https://community.tulip.co/u/fti)\
**Post date:** [February 25, 2025, 4:38pm UTC](https://community.tulip.co/t/add-a-screen-for-tulip-account-owner-to-have-visibility-of-available-enabled-feature-flags/11560/5 "2025-02-25T16:38:21Z")

</div>

Hello @kevin.kononenko.

Unfortunately I know neither what you are referring to nor where to find it ☹

Would you mind rephrasing this?

---

<div class="post-metadata">

**Author:** ![kevin.kononenko](https://sea2.discourse-cdn.com/flex020/user_avatar/community.tulip.co/kevin.kononenko/32/32_2.png) [@kevin.kononenko](https://community.tulip.co/u/kevin.kononenko)\
**Post date:** [February 25, 2025, 4:49pm UTC](https://community.tulip.co/t/add-a-screen-for-tulip-account-owner-to-have-visibility-of-available-enabled-feature-flags/11560/6 "2025-02-25T16:49:59Z")

</div>

So when we release a new LTS version of Tulip to our customers, we also give them an “IQ Certificate” which is meant to prove the integrity of the release. In other words, it has been set up in the way that it was intended. This must match across dev, test and prod instances. This is a PDF document. Have you seen one before?

---

<div class="post-metadata">

**Author:** ![fti](https://avatars.discourse-cdn.com/v4/letter/f/fbc32d/32.png) [@fti](https://community.tulip.co/u/fti)\
**Post date:** [February 27, 2025, 7:39am UTC](https://community.tulip.co/t/add-a-screen-for-tulip-account-owner-to-have-visibility-of-available-enabled-feature-flags/11560/7 "2025-02-27T07:39:17Z")

</div>

@kevin.kononenko I think all the instances I manage use standard releases so I guess it’s normal that I didn’t receive any IQ certificate.

I must confess I fail to see the relationship with this question and this topic (visibility of feature flags)?

---

<div class="post-metadata">

**Author:** ![kevin.kononenko](https://sea2.discourse-cdn.com/flex020/user_avatar/community.tulip.co/kevin.kononenko/32/32_2.png) [@kevin.kononenko](https://community.tulip.co/u/kevin.kononenko)\
**Post date:** [February 27, 2025, 1:11pm UTC](https://community.tulip.co/t/add-a-screen-for-tulip-account-owner-to-have-visibility-of-available-enabled-feature-flags/11560/8 "2025-02-27T13:11:22Z")

</div>

Understood. The IQ certificates contain a summary of the feature flag configuration, so that is our standard method of communicating this.

So, if we had an automated way for you to generate an IQ certificate at any time for each instance, would that solve the problem?

---

<div class="post-metadata">

**Author:** ![fti](https://avatars.discourse-cdn.com/v4/letter/f/fbc32d/32.png) [@fti](https://community.tulip.co/u/fti)\
**Post date:** [February 27, 2025, 2:11pm UTC](https://community.tulip.co/t/add-a-screen-for-tulip-account-owner-to-have-visibility-of-available-enabled-feature-flags/11560/9 "2025-02-27T14:11:40Z")

</div>

@kevin.kononenko Displaying flags in a webpage would be more user-friendly but if you want a solution that’s quick-and-easy to implement, that would work for me. I don’t check flag configuration often so I wouldn’t mind generating an IQ certificate.

By the way, what does IQ stands for?

---

<div class="post-metadata">

**Author:** ![kevin.kononenko](https://sea2.discourse-cdn.com/flex020/user_avatar/community.tulip.co/kevin.kononenko/32/32_2.png) [@kevin.kononenko](https://community.tulip.co/u/kevin.kononenko)\
**Post date:** [February 27, 2025, 2:16pm UTC](https://community.tulip.co/t/add-a-screen-for-tulip-account-owner-to-have-visibility-of-available-enabled-feature-flags/11560/10 "2025-02-27T14:16:33Z")

</div>

You can learn more about the theory here: [Installation Qualification (IQ) | Propel Glossary](https://www.propelsoftware.com/glossary/installation-qualification-iq)

Also, I am curious, how did this come up for you? Is there one particular feature flag that was varying across instances and creating different behavior, or is it just a general need for reporting?

---

<div class="post-metadata">

**Author:** ![fti](https://avatars.discourse-cdn.com/v4/letter/f/fbc32d/32.png) [@fti](https://community.tulip.co/u/fti)\
**Post date:** [February 27, 2025, 2:59pm UTC](https://community.tulip.co/t/add-a-screen-for-tulip-account-owner-to-have-visibility-of-available-enabled-feature-flags/11560/11 "2025-02-27T14:59:06Z")

</div>

@kevin.kononenko It’s closer to one (or several) flag(s) varying across my instances; I have no reporting needs for now. In my case, I had to enable some flags on some instances but not others. I asked for this at different moments time and sometimes for different reasons. Seeing this list of flags would allow me to:

- be reminded of which flags have been enabled or not so far on a given instance
- be reminded of which features are enabled by flags and which ones are always there
- figure out why something can be done on an instance and not on another
- know what optional features are available, some being potentially interesting for my customers

---

<div class="post-metadata">

**Author:** ![mdutta](https://avatars.discourse-cdn.com/v4/letter/m/4bbf92/32.png) [@mdutta](https://community.tulip.co/u/mdutta)\
**Post date:** [December 9, 2025, 4:30am UTC](https://community.tulip.co/t/add-a-screen-for-tulip-account-owner-to-have-visibility-of-available-enabled-feature-flags/11560/12 "2025-12-09T04:30:48Z")

</div>

Hi Tulip Team, It would be nice to have the visible/hide any feature based on Feature flag. Currently as it is mentioned in LTS15 Release notes that a feature flag can be enabled/disabled based on Feature flag. But it is necessary to make certain feature ( UI component) visible/hide based on feature flag. and resize some UI components if any other feature is not present to utilize the real estate of the UI

---

<div class="post-metadata">

**Author:** ![kevin.kononenko](https://sea2.discourse-cdn.com/flex020/user_avatar/community.tulip.co/kevin.kononenko/32/32_2.png) [@kevin.kononenko](https://community.tulip.co/u/kevin.kononenko)\
**Post date:** [December 10, 2025, 7:19pm UTC](https://community.tulip.co/t/add-a-screen-for-tulip-account-owner-to-have-visibility-of-available-enabled-feature-flags/11560/13 "2025-12-10T19:19:30Z")

</div>

Hi Madhab, thanks for sharing this. Is there one particular feature where this is bothersome?

---

<div class="post-metadata">

**Author:** ![mdutta](https://avatars.discourse-cdn.com/v4/letter/m/4bbf92/32.png) [@mdutta](https://community.tulip.co/u/mdutta)\
**Post date:** [December 10, 2025, 7:34pm UTC](https://community.tulip.co/t/add-a-screen-for-tulip-account-owner-to-have-visibility-of-available-enabled-feature-flags/11560/14 "2025-12-10T19:34:03Z")

</div>

Hi Kevin, Here by “feature” I mean the UI controls or functionalities of my app. I want to make those UI control Or the functionalities visible / hide based on the feature flag which I want to mark as true or false in a tulip table

---

<div class="post-metadata">

**Author:** ![kevin.kononenko](https://sea2.discourse-cdn.com/flex020/user_avatar/community.tulip.co/kevin.kononenko/32/32_2.png) [@kevin.kononenko](https://community.tulip.co/u/kevin.kononenko)\
**Post date:** [December 10, 2025, 7:52pm UTC](https://community.tulip.co/t/add-a-screen-for-tulip-account-owner-to-have-visibility-of-available-enabled-feature-flags/11560/15 "2025-12-10T19:52:23Z")

</div>

I see! Based on the response here, we do not currently have that on our roadmap: [Disable and hide Input Widgets](https://community.tulip.co/t/disable-and-hide-input-widgets/2502)
