Tables, records and exports

The OAuth scope does not replace current permissions on the table, the source files or the destination folder. Members read their own records; restricted table read grants let authorized office staff read other members’ records. Saving records and producing an export are independent operations.

To let office staff read every record without allowing changes, use grant_set with tableId, the receiving member or team and level: "read". Check grants with grants_list and tableId; revoke with grant_set and level: null. Each call takes a single target, never tableId together with file, folder or portal identifiers.

In writes, requestId is any key you choose; repeat the same key to repeat the same request. An identical retry returns the revision or result originally accepted; reusing the key with other content or another user is a conflict. Use expected revisions to avoid overwriting concurrent changes.