If I add entire domain as users, will they see Latest or Stable version?

When I add users individually by e-mail address, I can set if theyโ€™ll be seeing the stable or latest version of the app. But such option doesnโ€™t exist when I add an entire domain. What will the entire domain see?

0 12 434
12 REPLIES 12

Does anyone know the answer to this question?

I suspect itโ€™s related to โ€œControl rollout of latest versionโ€ in the Versions Tab of the โ€œManageโ€ menu but Iโ€™d like to be sure.

Thanks,

Andy

Steve
Platinum 4
Platinum 4

Users given access by merit of being in the domain will get the latest version. The only way to give a user the stable version is to add an individual user entry for them in the app editor. There is no way to change this behavior.

I believe this is also true to the case we use Amazon cognito for app auth, am I correct?

Iโ€™d expect adding the users authenticated via Cognito would be treated as users included by merit of their domain. So I would expect Cognito-authenticated users to get the latest version unless a specific user entry is (also) added in the app editor.

I would assume that user would get the โ€œdefaultโ€ version, which is defaulted to being โ€œlatestโ€, instead of explicitly being set to โ€œlatestโ€. Would you say that is true? Is there no way to change what the โ€œdefaultโ€ version is?

Nope.

Let me try to clarify a couple of things โ€ฆ

a) if you are adding an authentication provider and using domain authentication, then you specify app access control for individual groups, and for each group, you can specify the app version (stable or latest) and the user role for users in that group
b) if you are just using the Users pane and adding an entire domain โ€œfoo.comโ€, then you donโ€™t get to explicitly specify roles and groups. This is where the defaults should kick in. If a Stable version of the app has been defined, by default, everyone gets the stable version (as correctly pointed out earlier, this is controlled by the โ€œControl rollout of latest versionโ€ option โ€” so as that percentage is increased, more users see the latest version). If you need any specific user to see the latest version or to stay on the stable version explicitly, you add them explicitly to the Users list

Anyway, this is how it is supposed to work, I believe. We have an internal thread going now to double-check and verify this.

Thanks for the clarification!

Thanks Praveen,

We are just adding the whole domain in the users pane. I am pretty sure everyone is getting the stable version as I had to break the latest version of an app yesterday and no-one complained.

Thanks for picking up on this. This was the first time weโ€™d used domain authentication. I recommend this is added into the main documentation as it was a bit scary when I realised that when I clicked โ€œSaveโ€ with breaking changes, I wasnโ€™t completely sure what was going to happen to existing users!

Best regards,

Andy

@praveen , Iโ€™ve come across one additional point that that I could use some clarification on.

See my domain auth setup below:

Notice that there are 2 groups โ€œAll Usersโ€ and โ€œAppsheet Devsโ€, with different role and version settings. All of the user in the โ€œAppsheet Devsโ€ group, will also be in the โ€œAll Usersโ€ group. In these cases, where a user is in multiple groups, how will Appsheet assign the role and version here. Is it prioritized based on the order that the groups are set up here (I notice they can be click-and-dragged up and down)?

Update from support here for anyone else that needs to know (regarding my last post):

We loop through the groups and return the first match. So yes, order matters. The more specific group (โ€œAppsheet Devsโ€ in this case) should be first.

Iโ€™m not fully catching up with, but AppSheet devs group is placed on the bottom rather than top, but why it comes first for this loop? Bottom comes first ?

Top Labels in this Space