General settings when I come in here, I can choose gone is for me. So this will be for my web app, my application my service, I can choose a sign in logo. And I can choose the favicon, which will show up here. And it’s basically a way for me to rebrand rebrand Cyclr. So it fits my website’s image, my website, its identity, right my brand identity.
You can change the noun. So you might not have cycles as your noun, you might have templates, if you’re embedding it. If you’re creating a cycle, or you’re launching a cycle, you might want to change that from create, it might not fit necessarily in terms of the verbiage on your website, or how your website or application comes across.
You can also choose whether end users and things are embedded have access to custom connectors, have notification webhooks. And you can see here, there’s also a couple of things as well as you can enable iframe embedding.
So what this means is, when you embed the product, it just sits in as an iframe and instead of them having to come here to Cyclr. It just sits out an iframe and they can they don’t have to leave your website to be able to use it.
You can surface the site for help links as well. Now, it might be the case that you don’t want your users to come to our help desk. So you hide that help link. And then here, you just need to want this, what we’ll be using the iframe, so what applications who can embed it, etc.
That way, it doesn’t mean anyone can just have your version embedded of Cyclr, should they find the code for the iframe and decide I’ll actually I’m going to take this and put this in and sell this to my users via your platform, so on. And they can just use my account, you choose who has access.