Hi everyone,
I frequently encounter a little problem with both SeaTable Cloud and Enterprise v5.1.9 (self-hosted): I often have to create universal Apps with a single record page and to send the URL of a specific record for one of my collaborators to check/modify. When accessing this link once logged in, no problem, everything works fine, but if the user is not already logged in, (s)he is redirected to the login page (nice!) but once logged in, the record displayed is not the sent url links to, but the first record in the table.
This is somewhat problematic, because it can either be confusing for the user or cause a privacy problem if the user shouldn’t be able to access another record (even if I’m aware that using a single record page with such privacy considerations is not really the best solution).
I can’t imagine any workaround as it is really a behaviour of the tool, so for now I explicitly specify that the user must first log in and only then access the url of the specific record, but let’s face it, who reads these kinds of instructions ?
Bests,
Benjamin