[Feature Request] Policy settings (Specifically to disable the First Steps page)

[AE720]

It would be amazing if there was a way via policy to disable the launch of a new tab when first installing Screenity just as with a json file.

[alyssaxuu]

You can disable the steps page opening by simply removing these lines of code, and then creating a new build as per the README instructions.

As per making it an actual "feature" - I guess I'm not sure what exactly the use case would be, are you installing / uninstalling frequently?

[AE720]

You can disable the steps page opening by simply removing these lines of code, and then creating a new build as per the README instructions.

As per making it an actual "feature" - I guess I'm not sure what exactly the use case would be, are you installing / uninstalling frequently?

Thanks for the response. It's for enterprise purposes. More ideal when pushing it out to users en masse.

[alyssaxuu]

You can disable the steps page opening by simply removing these lines of code, and then creating a new build as per the README instructions.
As per making it an actual "feature" - I guess I'm not sure what exactly the use case would be, are you installing / uninstalling frequently?

Thanks for the response. It's for enterprise purposes. More ideal when pushing it out to users en masse.

I see! Since this is for enterprise use and distributing to users, just a quick check—Screenity is GPLv3, so any modifications would need to be open-sourced under the same license. Are you planning to publish your changes?

If you need something more tailored for enterprise, feel free to reach out at alyssa@screenity.io, happy to chat!

[AE720]

You can disable the steps page opening by simply removing these lines of code, and then creating a new build as per the README instructions.
As per making it an actual "feature" - I guess I'm not sure what exactly the use case would be, are you installing / uninstalling frequently?

Thanks for the response. It's for enterprise purposes. More ideal when pushing it out to users en masse.

I see! Since this is for enterprise use and distributing to users, just a quick check—Screenity is GPLv3, so any modifications would need to be open-sourced under the same license. Are you planning to publish your changes?

If you need something more tailored for enterprise, feel free to reach out at alyssa@screenity.io, happy to chat!

Nothing that convulsed! Just think pushing the extension our for faculty to utilize as an end user. No modifications. The main intent is to keep the OOBE as clean as possible as powerwashing is a common troubleshooting step and makes the onboarding process easier.

[alyssaxuu]

Nothing that convulsed! Just think pushing the extension our for faculty to utilize as an end user. No modifications. The main intent is to keep the OOBE as clean as possible as powerwashing is a common troubleshooting step and makes the onboarding process easier.

Got it, in that case if there's no modifications there's no problem in that regard - I just wanted to confirm as you mentioned enterprise use and mass distribution :)

But yes, from a self-hosting POV I can see some sort of option for that embedded in the code to be useful, I will consider adding it in for sure!