Tetap teratur dengan koleksi
Simpan dan kategorikan konten berdasarkan preferensi Anda.
Kolom pengguna yang valid untuk kueri grup dinamis
Halaman ini menguraikan kolom dan fitur CEL yang didukung dan dapat
digunakan dalam kueri keanggotaan.
Kolom pengguna
Kolom berikut dari resource
User Admin SDK
dapat digunakan dalam kueri keanggotaan.
Kolom
Sub-kolom
addresses
country
country_code
custom_type
extended_address
locality
po_box
postal_code
primary
region
street_address
type
archived
boolean
change_password_at_next_login
boolean
is_2sv_enforced
boolean
is_enrolled_in_2sv
boolean
is_mailbox_setup
boolean
locations
area
building_id
custom_type
desk_code
floor_name
floor_section
type
organizations
cost_center
custom_type
department
description
domain
location
name
primary
symbol
title
type
relations
custom_type
type
value
emails
address
custom_type
primary
type
external_ids
custom_type
type
value
gender
address_me_as
custom_gender
type
ims
custom_protocol
custom_type
standard_protocol
primary
type
value
keywords
custom_type
type
value
languages
language_code
name
family_name
given_name
value
phones
custom_type
primary
type
value
suspended
boolean
suspension_reason
custom_type
type
value
websites
custom_type
primary
type
value
Atribut jenis
Atribut type dari tabel sebelumnya dicocokkan menggunakan nilai enum, bukan representasi stringnya. Daftar berikut mendokumentasikan representasi string setiap
jenis ke nilai enum yang sesuai.
Atribut
Nilai enum
Representasi string
Alamat
0
tidak diketahui
1
khusus
2
rumah
3
bekerja
4
lainnya
Lokasi
0
default
1
khusus
2
meja
Organisasi
0
tidak diketahui
1
bekerja
2
school
3
khusus domain
Relasi
12
pengelola
Email
0
tidak diketahui
1
khusus
2
rumah
3
bekerja
4
lainnya
ID Eksternal
0
tidak diketahui
1
khusus
2
akun
3
customer
4
jaringan
5
organisasi
6
login_id
Gender
0
tidak diketahui
1
laki-laki
2
perempuan
3
lainnya
Protokol standar IMS
0
default
1
protokol kustom
2
tujuan
3
msn
4
yahoo
5
skype
6
qq
7
gtalk
8
icq
9
jabber
10
rapat net
Jenis IMS
0
tidak diketahui
1
khusus
2
rumah
3
bekerja
4
lainnya
Kata kunci
0
tidak diketahui
1
khusus
2
misi
3
pekerjaan
4
outlook
Ponsel
0
tidak diketahui
1
khusus
2
rumah
3
bekerja
4
lainnya
5
faks rumah
6
faks kantor
7
seluler
8
pager
9
faks lainnya
10
nomor utama perusahaan
11
asisten
12
car
13
radio
14
isdn
15
callback
16
telex
17
tty tdd
18
nomor seluler kantor
19
pager kantor
20
utama
21
grand central
22
Voice Perusahaan
Alasan Penangguhan
1
admin
2
di bawah 13 tahun
3
login web diperlukan
4
penyalahgunaan
5
penyalahgunaan—dapat dipulihkan oleh admin
Situs
0
tidak diketahui
1
halaman penginstalan aplikasi
2
blog
3
khusus
4
ftp
5
rumah
6
beranda
7
lainnya
8
profil
9
reservations
10
resume
11
bekerja
Kolom unit organisasi
Anda juga dapat membuat kueri keanggotaan menggunakan kolom orgUnitId untuk menyertakan semua pengguna yang merupakan bagian dari unit organisasi tersebut, secara langsung atau tidak langsung. Untuk mengetahui informasi
selengkapnya tentang cara mengambil nilai orgUnitId, lihat
dokumentasi referensi Admin SDK.
Sampel kueri
Semua pengguna langsung di unit organisasi tertentu:
user.org_unit_id==orgUnitId('03ph8a2z1enx4lx')
Semua pengguna langsung dan tidak langsung dalam unit organisasi tertentu:
Ganti MANAGER_ID dengan ID pengguna unik
pengelola. Anda dapat mengambil ID ini dengan
AdminSDK Directory API
menggunakan alamat email pengelola sebagai userKey.
[[["Mudah dipahami","easyToUnderstand","thumb-up"],["Memecahkan masalah saya","solvedMyProblem","thumb-up"],["Lainnya","otherUp","thumb-up"]],[["Sulit dipahami","hardToUnderstand","thumb-down"],["Informasi atau kode contoh salah","incorrectInformationOrSampleCode","thumb-down"],["Informasi/contoh yang saya butuhkan tidak ada","missingTheInformationSamplesINeed","thumb-down"],["Masalah terjemahan","translationIssue","thumb-down"],["Lainnya","otherDown","thumb-down"]],["Terakhir diperbarui pada 2025-09-03 UTC."],[[["\u003cp\u003eThis document lists the supported user fields from the Admin SDK's \u003ccode\u003eUser\u003c/code\u003e resource that can be used in dynamic group membership queries, which are available to certain Google Workspace and Cloud Identity accounts.\u003c/p\u003e\n"],["\u003cp\u003eCustom user fields are supported in queries, provided that the schema already exists within \u003ccode\u003euser.custom_schemas\u003c/code\u003e, as detailed in the linked documentation.\u003c/p\u003e\n"],["\u003cp\u003eThe document specifies which fields can be used and the sub-fields each one has, with the inclusion of \u003ccode\u003eboolean\u003c/code\u003e types and when a field has a \u003ccode\u003eprimary\u003c/code\u003e value that can only be evaluated as true.\u003c/p\u003e\n"],["\u003cp\u003eThe \u003ccode\u003etype\u003c/code\u003e attributes used in the user fields table are matched to enum values rather than string representations, and a table is provided mapping the string values to their corresponding enum values.\u003c/p\u003e\n"],["\u003cp\u003eMembership queries can also be performed using the \u003ccode\u003eorgUnitId\u003c/code\u003e field to include users directly or indirectly within a specified organizational unit, and the document also includes sample queries on how to retrieve users by their org unit, or managers.\u003c/p\u003e\n"]]],[],null,["# Valid user fields for dynamic group queries\n===========================================\n\nThis page outlines supported fields and features of CEL that can be\nused in a membership query.\n| **Note:** Dynamic groups are only available to Google Workspace Enterprise Standard, Enterprise Plus, Enterprise for Education, and Cloud Identity premium accounts.\n\nUser fields\n-----------\n\nThe following fields from the Admin SDK's\n[`User`](https://developers.google.com/admin-sdk/directory/reference/rest/v1/users)\nresource can be used in membership queries.\n| **Note:** Custom user fields are also supported as long as the schema already exists in `user.custom_schemas`. See [Manage custom user fields](https://developers.google.com/admin-sdk/directory/v1/guides/manage-schemas) for more information about creating a custom schema.\n\n| **Note:** When a field has a `primary` value, that value can only be evaluated as a true expression. For example: \n| `user.addresses.exists(addr, addr.primary == true)\"`\n\n### Type attributes\n\nThe `type` attributes from the previous table are matched using enum values\ninstead of their string representations. The following list documents each\ntype's string representation to the corresponding enum value.\n\nOrganizational unit fields\n--------------------------\n\nYou can also query memberships using the `orgUnitId` field to include all\nusers who are part of that organizational unit, directly or indirectly. For more\ninformation about retrieving the `orgUnitId` value, see the\n[Admin SDK reference documentation](https://developers.google.com/admin-sdk/directory/reference/rest/v1/orgunits).\n\n### Sample queries\n\n- All direct users under a given organizational unit:\n\n user.org_unit_id==orgUnitId('03ph8a2z1enx4lx')\n\n- All direct and indirect users under a given organizational unit:\n\n user.org_units.exists(org_unit, org_unit.org_unit_id==orgUnitId('03ph8a2z1khexns'))\n\nOther query types\n-----------------\n\n- All users managed by a specific individual:\n\n user.managers.exists(manager, manager.user_id == userId('\u003cvar translate=\"no\"\u003eMANAGER_ID\u003c/var\u003e'))\n\n Replace \u003cvar translate=\"no\"\u003eMANAGER_ID\u003c/var\u003e with the manager's unique\n user ID. You can retrieve this ID with the\n [AdminSDK Directory API](https://developers.google.com/admin-sdk/directory/reference/rest/v1/users/get)\n using the manager's email address as `userKey`."]]
