Hi to all,
My problem is as follows:
I need to generate several "similar" customer-facing public status pages that rely on a shared baseline of components (others will be different).
My approach is:
- generate one "baseline status page" with the entire list of components I would need for all the customer-facing status pages.
- As indicated in the User Documentation, ask Technical Support to have this baseline status page shared as 3rd party status page.
- generate the customer-facing status pages as a combination of 3rd party components from the baseline status page.
Questions:
1. does this approach make sense?
2. Any alternative?
3. Can I have my "baseline status page" as private/internal and still be shared for 3rd party component integration?
Thanks in advance
This is Tejaswi from Statuspage Team and here to help.
If you wish to reuse the same components on multiple statuspage., You can add them as a third party components and manage them from a single base statuspage and it will be updated in all the other statuspage as well.
Once a Public facing statuspage components can be added as a third party components and we cannot add the components from a private page.
If you have further queries, Please feel free to reach out to us by logging a ticket.
Kind Regards,
Tejaswi
Hi Tejaswi, thanks a lot for your help. I think this approach will work for us.
I will open a ticket to share the base statuspage as 3rd party component once we have created it.
thanks a lot again.
M
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.