EcoSapien

One-time website connection

Use the Drive
you already have.

Your personal Google account and its existing storage allowance work for this workspace. Google asks the website owner to create a public connection ID before the first sign-in. You do this once.

  1. Create a Google project.

    Open Google Cloud → Create a project ↗, sign in with your Google account and name the project EcoSapien Applications. Select that project in the top bar when it is ready.

  2. Enable Google Drive API.

    Open Google Drive API ↗ in the selected project and choose Enable. The API connects this website to your existing Drive; it does not create a different storage account.

  3. Set up Google Auth Platform.

    Open Google Auth Platform ↗ and choose Get started if prompted. Use EcoSapien Applications as the app name and your own email for support and developer contact.

    For a personal Google account, choose the External audience. For your own use, leave publishing status as Testing and add the Google email you will sign in with under Audience → Test users. Only accounts you list can use the app while it is in Testing.

    In Branding, use these website details if Google requests them:

    Homepage
    https://www.ecosapien.de/databases.html
    Privacy policy
    https://www.ecosapien.de/application-privacy.html
    Authorised domain
    ecosapien.de

    In Data Access → Add or remove scopes, add this single scope:

    https://www.googleapis.com/auth/drive.file

    It lets the workspace manage files it creates. This implementation does not request access to everything in your Drive. Google may request additional branding or domain verification depending on the project’s settings.

  4. Create the website client ID.

    Open Clients ↗, choose Create client and select Web application. Name it EcoSapien website.

    Under Authorised JavaScript origins, add exactly:

    https://www.ecosapien.de

    Use only the origin above: no page path or trailing slash. This popup sign-in flow does not need an authorised redirect URI. Select Create.

  5. Copy the public ID into the website.

    Copy the Client ID ending in .apps.googleusercontent.com. Return to Databases → Sign in with Google → Connect this website to Google. Paste it and select Save connection.

    Then choose Continue with Google, select your account and approve the requested file access. The site creates a restricted EcoSapien Applications folder inside My Drive.

    The public ID is saved in this browser. To use the same connection on every device, the website maintainer can put this public ID in assets/google-drive-config.js. A client secret must never be pasted into the website or its GitHub repository.

Upload your finished files.

Open Databases and find your programme. Beside its progress bar, choose the document type and select Upload. Files are organised as EcoSapien Applications → programme → document type. Use Download to retrieve the selected file, or Open selected file to view it in Drive. Manage documents, notes & deadline opens the full checklist and planning fields. Each upload can be up to 100 MB; PDF is usually the best final format.

The Shared resources section holds reusable transcripts, certificates and references under Shared documents → document type. Programme-specific uploads take priority over shared files. A replacement keeps the earlier version in Drive. For an existing file linked from outside this workspace, use Open in Drive if direct download is unavailable.

Progress saves to Drive automatically. Wait for All changes saved before closing the page. Sign in with the same Google account on another device, and use Sync now when you want to refresh an already-open page. Google access expires periodically; choose Reconnect to Google when prompted.

If Google shows an error
  • Origin mismatch: check that the client is a Web application and its authorised origin is exactly https://www.ecosapien.de. Google configuration changes can take time to apply.
  • Access denied / test user: add the exact account you selected under Audience → Test users.
  • Drive API disabled: enable Drive API in the same project that owns the client ID.
  • Popup blocked: allow sign-in popups for this website, then select Continue with Google again.
  • Shared or moved folder: keep EcoSapien Applications directly inside My Drive and keep its folder and subfolder sharing Restricted.
  • Different Google account on reconnect: reconnect with the original account or save your work and sign out before switching accounts.
For local development

Add http://localhost and http://localhost:8765 as additional authorised JavaScript origins, then preview the site at that exact hostname and port. Use a separate development OAuth client where practical. A downloaded file:// research copy cannot run Google sign-in.

Google’s official references: Client ID setup · Popup token model · Drive file permissions.

Return to my applications →