Org Admins Can Now Curate the Navigator Experience

So hopefully that screen sharing is working. So Are you showing a new feature valid around the views within Navigator? So we've had some feedback that's come from the customers during the AP around the fact that the org admins can't visualize what their end users are going to see out of the box.

And they'd also like a way of standardizing the content they'd also see. So the idea of an org admin creating a view solves this. So they'd be able to pick predefined configuration, whether that be the panels, actions, or sections.

And they'd also then be able to do some simple level of targeting, whether that be a group of members, say like 5 individuals from your HR team potentially, or giving it to all the org admins via groups. or you can actually do a very global one and just target the entire organization. So with that in mind, the everyday user would come into the system. They would see the EVO view, which would be driven by the defaults from personas.

They'd also see some other views as well, which the org admins have made. So the end user will get a sense of what the quick objects are, what the system can do for them. And then hopefully with this would then drive some further discovery where they'd go and create their own views, do their own configurations, and hopefully optimize their workflows accordingly.

So I'm in pre-prod. This is a very small organization. It's just myself.

So in groups, I've got these set up just to show the functionality. So this one here is targeting org admins. I've got another one which is targeting users.

So you can imagine, hopefully in production for our customers, they've already got groups set up. They're already using them. Doing their different things like your HR, for example.

So here in Navigator, I've only got the Evo experience, so this will be driven by personas. And if I come over to the admin screen. They've now got a new option for managing their views.

So here is where all org admins within this org can see what views are currently in the system and can all collaborate together on one view and just manage the distribution and so on. So here we've kind of got a nice light touch of a preview of what the navigator screen looks like. So hopefully this will help the admins understand and give them a simple preview of what's going to happen for their end users.

So I'm just going to make a simple admin view. And you can then set up your quick objects. So you've got all the standard behavior where you can expand, collapse, you can search.

Fairly standard stuff for navigator, same for filtering. So at the moment we've got a limit of 6, but we are going to probably revisit that limit and just try and improve it over time. As you can see, me adding items are just automatically reflected behind as well.

Same for like the reordering. So reordering works, you can remove items. You can also reorder here too. which could be quite nice when you're on the fly, just want to tweak some stuff quickly.

I'll just add some configuration to the other sections. So hopefully this kind of gives you an idea of what the screen would look like. So panels come down the side, quick actions go across the screen, and so on for sections.

We can then come to sharing. So here you've got your free options, so you can do members, but you can do up to 100 users. Or you can actually do your groups, so I'm just going to do admins, or you can actually do the entire org, so as you can see, you get a bit of feedback as well, so everything's persisted.

As you can see as well, this is going to be a locked layout, so what you set up here is what your end users will see. So if I now save this, so this is all in draft as well, so no user would have received this at the moment. So now I've got my different filters, could do different scopes and so on.

So hopefully help you manage when you've potentially got 10 views going on. We can also do some simple duplication. So here, it's took the entire config over.

So I'm just going to make a user view as well. And to show another feature, I'll just do that as well, so I'll have no distribution selected. And because I'm in draft, I'm able to do that.

So the idea is that you might start doing some creation, you know, come back to it an hour later, you'll finish it once you've got your group set up. So we're not going to block you because it's on your draft. It's not impacting any users yet.

But then if I come back here, we can actually see that the admin view, everything's set up accordingly. We're able to publish. But the user one, I've not shared it with anyone yet, so there is like a validation check happening.

So we get a bit of feedback here. So I would then come into here, edit again, update the distribution model. And resave.

And now if I just refresh just to prove that I've not received the admin view. So I've still got Evo. Nothing's happened yet.

And then come back, and if I then just publish these items. And now, if I reload, I should hopefully get the admin view and not the user, because the groups is clicking in. So, I've got my Evo, and now you can see I've got my admin view.

And now that configuration has come through. So every user who would receive this, because they're part of the group, they would now get this exact configuration. And it's purely read-only, so I can't do any configuration or any of that stuff.

And other things as well, if I'm on the admin. and I decide to unpublish the view or delete it, whatever the reason is. If I reload, the system should kick in, see it's not valid anymore, and then bring me back to the default experience, which is EVO. That's the first time I've had it do that.

OK, let's have a look into that.