You cannot use computed columns as row owners. You must use basic columns (such as text columns).
For example, if you want workers 1, 2, and 3 to have access to a specific job, you can create three basic text columns, each marked as a row owner column, and assign each worker’s email to a separate column. Alternatively, you can assign a role to each worker in the users table (make sure to map this role column to the user’s configuration in the application). Then, you can use this role in one or more columns, marked as row owner columns, within the relevant table.
You are going to have an issue with your user table. You have two rows for the same user. You should only have one. When the user updates their profile, they should be editing the existing row that was auto generated for them instead of adding a new row.
I see a ‘Role’ column and a ‘Hirer or Worker’ column in your user table. Which one have you configured for Role functionality? They both cannot be used for Roles. You can have multiple Row Owners on a table, but a user can only have one Role. (There is a loophole with Google sheets, but I won’t get into that to avoid confusion.)
I have both set as row owners right now. The issue is I cannot get my onboarding choice component to update the row table for workers as workers, because apparently choice components & actions cannot be used to update a users role and it must be done through an external api call instead.
OK. Since you are using the Role column for Role functionality, and it appears to be empty, any row owner columns in other tables that attempt to use a role instead of email won’t show anything because there is no matching role from the user table that matches a role entered into a row owner column.
Also, your profile is configured to use a boolean column as an image. Probably not affecting anything, but that is not a proper configuration. It should point to an image column