Gemini Customize brings reusable instructions and connected apps into a single area of Google’s assistant. The update, described in an October 21, 2026 announcement, makes those options easier to find. It does not mean that every integration shown in a demonstration is available in every country.
For someone asking how to personalise Gemini, the key distinction is between how the assistant responds and which tools it can access. Saving a preference does not authorise an external service, and connecting an app does not make every answer reliable.
Gemini Customize: what the new area brings together
The official Google Workspace announcement places skills and connected apps together. The menu is rolling out globally, while many external integrations remain restricted to English in the United States, with selected apps available in additional markets.
Seeing the menu in an account is therefore a useful first check, not confirmation that the full catalogue is usable. Language, country and account type can explain differences between an advertised example and the options on a particular screen.
The announcement is dated October 21, but its stated gradual rollout began on October 13. Publication date and account enablement are different milestones. Neither should be interpreted as proof that every user received every option simultaneously.
Skills and connected apps solve different problems
| Component | Purpose | What it does not establish |
|---|---|---|
| Skill | Reuse instructions for recurring tasks | Automatic access to external services |
| Connected app | Interact with an authorised service | Availability in every region |
| Customize | Organise personalisation options | Blanket permission for all actions |
| Work account | Use organisation-approved features | Permission to bypass company policy |
A skill might specify a document structure, information to highlight or a preferred tone. A connection instead concerns another service and the capabilities actually allowed for the account. These are related choices, but they should not be treated as interchangeable.
The subject sits alongside Agent Skills moving to AAIF, without being the same development. Shared terminology is not evidence that every instruction or integration can move unchanged between competing products.
How to distinguish missing access from a fault
The Gemini Customize help page describes Discover, Connectors and Skills, with signed-in adult users in supported languages and regions as its access baseline. Work accounts also depend on administrator-enabled access.
Before diagnosing a bug, record what is missing: the entire area, a particular skill or a specific app. These are different situations. Paying for a more expensive plan is not automatically the appropriate fix for a regional restriction or an organisational setting.
Check which account is active, particularly when personal and work profiles coexist in the same browser. Comparing accounts may help explain the difference, but it does not justify moving company documents into a personal account to get around a restriction.
When one integration is missing, check the support page for that particular app. Changing the interface language does not demonstrate that the service’s geographic, account and contractual requirements are also satisfied.
What organisations should evaluate
The Workspace administrator documentation explains that Gemini’s access to organisational services is subject to administrative controls. An option visible in an interface does not establish permission to use arbitrary business material.
For a team, the useful question is not how many connections can be enabled, but which ones genuinely support an agreed task. Each connection should have a purpose, an owner and a clear understanding of the information involved.
Commercial product access is also different from internal authorisation. Our coverage of OpenAI models on Google Cloud illustrates why catalogue availability, access and data handling need separate checks rather than one general assumption that a service is ready to use.
A useful example: a consistent software profile
Imagine turning public software descriptions into short profiles covering intended users, requirements and limitations. A reusable skill could preserve that structure. This is an illustrative evaluation scenario, not a test conducted by our newsroom.
There is no need to connect an entire mailbox or document archive at the start. Public sample material can show whether the assistant distinguishes known facts, missing information and uncertainty, instead of inventing content to complete every section.
Only then does it make sense to consider a connection that helps the task, provided that connection is available. Adding integrations without a measurable purpose increases the number of things to manage without demonstrating an improvement.
Permissions do not replace result checking
Gemini Customize can organise options, but instruction quality still matters. “Be accurate” is difficult to audit. A rule requiring sources, assumptions and unavailable fields to be separated gives a reviewer something more concrete to inspect.
Tasks with external consequences also need a stopping point. Drafting text, reading a document and sending a message are different operations. The appropriate confirmation depends on the action, not on whether everything happens within one conversation.
A sensible starting point remains a bounded task with non-sensitive material and human review before broader access is granted. The new area reduces scattered settings; it does not remove the responsibility to decide which tools and information an assistant should be allowed to use.
