Skip to main content
Begin with a functioning Studio library, a registered principal and the correct tenant context. AI never replaces workspace authorization. Keep every optional switch off until its dependencies and provider settings are ready.

Install the tables you need

For example, enable visual analysis and content extraction:
For chat, follow the separate assistant installation. Apply all migrations in each selected optional group when upgrading, rather than copying only its first create-table migration. Core Studio migrations are still required.

Four independent configuration areas

intelligence owns visual labels; search.content owns text/OCR projections; search.semantic configures Meilisearch embeddings; assistant owns chat. OCR uses the configured Google Vision credential but does not require enabling automatic visual tagging. A provider configured in Laravel ai.php does not configure intelligence.providers, and vice versa.

First-file rollout

Choose one non-sensitive managed asset in a test workspace. Register the CLI principal alias, grant only the required Studio ability and run the documented single-file command. Inspect its persisted result/state before testing automatic upload admission. Verify a denied user and a different workspace cannot access that result. Content on imported/external sources needs its explicit supported adapter; mounting it for browsing does not transfer ownership to an AI processor. Use operations for queue timeouts, failure handling and quotas. Use the provider guide to choose the correct credential namespace.