You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Is your feature request related to a problem or unsupported use case? Please describe?
Currently, Docs (collaborative document editor) and Drive (collaborative file-sharing platform) operate as separate applications with independent permission systems, sharing only OIDC identification for authentication. This separation creates friction for users who want to organize their documents into Drive folders directly from Docs.
For example:
A user creates a document in Docs and wants to save it to a specific folder in Drive.
Since the two apps are separate, the user must:
Save the document in Docs.
Open Drive in a new tab.
Locate the document.
Move it to the desired folder.
This workflow is inefficient, disrupts productivity, and increases the risk of misplacing documents.
Describe the solution you'd like
To address this, I propose implementing a cross-application interoperability layer that enables seamless interaction between Docs and Drive. We have to figure out how to implement this.
The goal of integration is:
→ Initial mockups (basis for reflection) (minor updates in progress by Robin)
Ability to create a document in Fichiers
Ability to move a document into a folder
Manage document permissions in both Fichiers AND Docs
Creating a document in Docs makes it appear at the root of Fichiers
Constraints
In its open-source version, Docs will come with a basic permission system (the one we currently have).
If the reuser also hosts Drive, they can choose to use Drive's permission system so that both apps are integrated.
In its LaSuite version, Docs will use Fichiers' permissions.
Docs is not developing a nested document system to facilitate integration between the two apps. However, the integration of Docs into Drive should not close the door on this possibility, which could be developed in the future.
Feature Request
Is your feature request related to a problem or unsupported use case? Please describe?
Currently, Docs (collaborative document editor) and Drive (collaborative file-sharing platform) operate as separate applications with independent permission systems, sharing only OIDC identification for authentication. This separation creates friction for users who want to organize their documents into Drive folders directly from Docs.
For example:
This workflow is inefficient, disrupts productivity, and increases the risk of misplacing documents.
Describe the solution you'd like
To address this, I propose implementing a cross-application interoperability layer that enables seamless interaction between Docs and Drive. We have to figure out how to implement this.
The goal of integration is:
→ Initial mockups (basis for reflection) (minor updates in progress by Robin)
Constraints