Repro: Create a Linked schema to audit tables or a query using audit tables in another container.
Expected: Able to view the audit data from the linked container
Actual: No data visible

Use case: Creating an ETL with a linked schema as the source. Audit logs provide the deleted rows source for the incremental filter. This is how we are currently telling EHR users to get Animal sources into Sample Manager.

Looks like the db query is still filtering on the source container, instead of the container defining the linked schema.

The problem is that linked schemas only grant ReaderRole:

https://github.com/LabKey/platform/blob/be8b4dcc22614540a58de4ce06e6c86728fc48dd/query/src/org/labkey/query/LinkedSchema.java#L589

but the audit tables check for CanSeeAuditLogPermission:

https://github.com/LabKey/platform/blob/36cbc31000b7f68df925634bf466d78d6ff3be0c/api/src/org/labkey/api/audit/query/DefaultAuditTypeTable.java#L144

A tacky but not insane idea would be to check the name of the source schema and if it's "auditLog", grant both ReaderRole and CanSeeAuditLogRole. You have to be a site admin to set up a linked schema, and presumably the reason you're creating it is to let people see the audit log.

Seems like a reasonable approach, thanks Josh. Susan do you mind estimating as the Audit feature owner and assigning back to triage?

Assigning to Josh since there's already a PR attached here.

Now merged to develop.

Assigning to Sweta as test feature owner of linked schemas.

Verified and test coverage added https://github.com/LabKey/testAutomation/pull/1166