Datashares grant data types, but there's no way to share a file. create_datashare takes fulcra_data_types + allowed_user_ids, while every file method — list_files, resolve_filepath, download_file, upload_file — is own-account only and takes no user id. Same on the CLI: share create requires --data-type, and no file subcommand accepts --user-id. Verified on 0.1.38.
So one account can't read another's file at all, and there's no file dimension in the share model to grant.
Request, in priority order:
- A file grant in the datashare model — share a path prefix (e.g.
reports/) the way a data type is shared today.
- Cross-account
list_files / resolve_filepath scoped to that grant, so a recipient can browse what they were given instead of being sent exact paths out of band.
Use case: multi-user apps that keep a creator's data separate from an end user's need file sharing that's scoped and browsable.
Datashares grant data types, but there's no way to share a file.
create_datasharetakesfulcra_data_types+allowed_user_ids, while every file method —list_files,resolve_filepath,download_file,upload_file— is own-account only and takes no user id. Same on the CLI:share createrequires--data-type, and nofilesubcommand accepts--user-id. Verified on 0.1.38.So one account can't read another's file at all, and there's no file dimension in the share model to grant.
Request, in priority order:
reports/) the way a data type is shared today.list_files/resolve_filepathscoped to that grant, so a recipient can browse what they were given instead of being sent exact paths out of band.Use case: multi-user apps that keep a creator's data separate from an end user's need file sharing that's scoped and browsable.