---
schema: dynamicmail.integration_terms_runtime_markdown.v1
asset_family: google-workspace-data-access
asset_id: google-workspace-data-access-zu-ZA
locale: zu-ZA
language: zu
country_code: ZA
text_direction: ltr
provider_key: google_workspace
integration_keys:
  - gmail_inbound
  - google_drive
requirement_key: google_workspace_data_access_terms
consent_version: "2026-06-02"
scope_codes:
  - https://www.googleapis.com/auth/gmail.readonly
  - https://www.googleapis.com/auth/drive
runtime_assets:
  - legal/integrations/google-workspace-data-access-zu-ZA.pdf
  - legal/integrations/google-workspace/zu-ZA/gmail-readonly-data-access.pdf
  - legal/integrations/google-workspace/zu-ZA/google-drive-data-access.pdf
---

# Google Workspace Data Access Terms - Gmail Inbound And Google Drive

## Imigomo yokufinyelela kudatha ye-Gmail readonly nge-scope ekhawulelwe

Le migomo ichaza ukufinyelela kwe-Gmail inbound i-DynamicMail ekucelayo lapho umsebenzisi noma umlawuli we-tenant ogunyaziwe exhuma ukwamukelwa kwemibhalo ye-Gmail inbound emisebenzini yemibhalo ye-tenant.

Ama-identity scopes e-Google Sign-In afana ne-`openid`, `email`, ne-`profile` ahlukile kule mvume yokufinyelela kudatha ye-Gmail. Ukungena ngemvume nge-Google akusho ukuthi ukufinyelela kwe-Gmail inbound kwamukelwe.

### Scope eceliwe

I-DynamicMail icela `https://www.googleapis.com/auth/gmail.readonly` kuphela lapho umsebenzisi noma umlawuli we-tenant ogunyaziwe exhuma ukwamukelwa kwemibhalo ye-Gmail inbound. Le scope ivumela i-DynamicMail ukubuka imilayezo ye-Gmail nezilungiselelo ze-akhawunti ye-Google exhunywe. I-DynamicMail isebenzisa le scope ekucubunguleni kwe-inbound okufundwayo kuphela, futhi ayiyisebenzisi ukuthumela, ukushintsha, ukususa, ukufaka ku-archive, ukufaka ilebula, noma ukuhambisa imilayezo ye-Gmail.

I-DynamicMail akufanele icele noma icubungule idatha ye-Gmail engahlobene nesici esibonakalayo sokwamukelwa kwemibhalo ye-inbound.

### Idatha i-DynamicMail engayifinyelela

Lapho i-Gmail inbound ixhunyiwe, i-DynamicMail ingafinyelela idatha ye-Gmail edingekayo ukuze ithole futhi icubungule imibhalo yebhizinisi engenayo, kuhlanganise nalokhu:

- ama-ID emilayezo, ama-ID ama-thread, ama-ID omlando, izinkomba zama-label, nama-sync cursors;
- umthumeli, umamukeli, isihloko, usuku, ama-header, nenye imethadatha yemilayezo;
- imizimba yemilayezo nama-snippets adingekayo ukuze kubonwe umongo wombhalo;
- okunamathiselwe namafayela asemgqeni angase aqukathe ama-invoyisi, izaziso, izivumelwano, amarisidi, noma eminye imibhalo ye-tenant;
- izilungiselelo ze-Gmail kuphela lapho i-Gmail API izidinga ngenxa ye-readonly scope noma ukuziphatha kokuvumelanisa i-akhawunti;
- idatha esuselwe kokuqukethwe kwe-Gmail, njengombhalo we-OCR, izinkambu zemibhalo ezihlaziyiwe, ama-label okuhlukanisa, imiphumela yokukhipha, izifinyezo, izehlakalo ze-audit, namarekhodi emibhalo.

### Kungani i-DynamicMail isebenzisa idatha ye-Gmail

I-DynamicMail isebenzisa idatha ye-Gmail readonly ukuze inikeze umthombo we-Gmail inbound okhethwe yi-tenant. Izinhloso ezihlosiwe yilezi:

- ukuthola imilayezo engenayo engase iqukathe imibhalo yebhizinisi ye-tenant;
- ukungenisa okunamathiselwe noma okuqukethwe kwemilayezo i-tenant ekhetha ukukucubungula;
- ukukhipha, ukuhlukanisa, nokuhambisa imibhalo emisebenzini ye-DynamicMail;
- ukuvumelanisa isimo se-sync ukuze umlayezo ofanayo ungangeniswa kaningi;
- ukubonisa isimo sokuxhuma, se-sync, nesokucubungula kubasebenzisi be-tenant abagunyaziwe;
- ukuxazulula izinkinga, ukuphepha, i-audit, nemisebenzi yokuthobela okusemthethweni evunyelwe izinqubomgomo ezifanele nesivumelwano se-tenant.

I-DynamicMail akufanele ithengise idatha ye-Gmail, iyisebenzisele ukukhangisa noma i-retargeting, iyidlulisele kuma-data brokers, iyisebenzisele ukubheka abantu, noma iyisebenzisele ukunquma ukufaneleka kwesikweletu noma ukufaneleka kokubolekwa.

### Ukugcinwa

I-DynamicMail igcina idatha esuselwe ku-Gmail kuphela uma kudingeka ngenxa yesici esibonakalayo semibhalo ye-inbound, izilungiselelo ze-tenant zokugcinwa kwemibhalo, amarekhodi e-audit, ukuphepha, ukuphatha izingxabano, noma ukuthobela okusemthethweni. Ama-OAuth tokens nemethadatha ye-sync kugcinwa kuphela ngesikhathi kudingeka ukuze umthombo we-Gmail inbound oxhunyiwe usebenze noma ukuze kugcinwe amarekhodi e-audit adingekayo.

Okuqukethwe kwemilayezo ye-Gmail okuluhlaza, okunamathiselwe, nedatha yemibhalo esuselwe kukho kufanele kususwe noma kwenziwe kungaziwa lapho kungasadingeki enjongweni edaluliwe, ngaphandle uma isibopho sezomthetho, sokuphepha, se-audit, noma sokugcinwa kwe-tenant sidinga ukuqhubeka nokugcinwa.

### Ukususwa

Umsebenzisi noma umlawuli we-tenant ogunyaziwe angacela ukususwa kwedatha egcinwe ku-cache esuselwe ku-Google, okunamathiselwe okungenisiwe, umbhalo okhishiwe, namarekhodi emibhalo asuselwe kukho. I-DynamicMail kufanele isuse noma yenze kungaziwa idatha eceliwe lapho izilungiselelo ze-tenant zokugcinwa kwemibhalo nomthetho osebenzayo zikuvumela.

Ukususa amarekhodi angenisiwe e-DynamicMail akususi ngempela i-imeyili noma okunamathiselwe kwayo kwasekuqaleni ku-Gmail, ngoba i-Gmail readonly scope ayiniki i-DynamicMail imvume yokushintsha noma ukususa imilayezo ye-Gmail.

### Ukuhoxisa nokunqamula uxhumano

I-tenant inganqamula i-Gmail inbound ku-DynamicMail. Ngemuva kokunqamula uxhumano noma ukuhoxiswa kwemvume yasendaweni, i-DynamicMail kufanele iyeke ukusebenzisa ama-OAuth tokens agciniwe e-Gmail inbound futhi kufanele iyeke ukufunda imilayezo eyengeziwe ye-Gmail ku-akhawunti exhunywe.

Umnikazi we-akhawunti ye-Google naye angahoxisa ukugunyazwa kwe-app kuzilungiselelo ze-akhawunti ye-Google. Uma ukugunyazwa kwe-Google kuhoxisiwe, i-DynamicMail kufanele imise ukufinyelela kwe-Gmail API lapho ukuvuselelwa kwe-token noma ama-API calls ehluleka, futhi uxhumano kufanele luboniswe njengolunqamukile noma oludinga ukuxhunywa kabusha.

Ukuhoxiswa kwasendaweni akususi ngokuzenzakalelayo imibhalo ye-DynamicMail esivele ingenisiwe. Lawo marekhodi aphathwa ngemithetho yokususwa nokugcinwa engenhla.

### Ukusetshenziswa kwe-AI, OCR, nokukhipha

I-DynamicMail ingasebenzisa i-OCR, parsing, ukuhlukanisa, ukufingqa, nokunye ukucubungula okusizwa yi-AI kokuqukethwe kwemilayezo ye-Gmail nokunamathiselwe, kuphela ukuze inikeze noma ithuthukise umsebenzi obonakalayo wemibhalo ye-inbound ye-tenant. Idatha ye-Gmail nedatha esuselwe kuyo akufanele isetshenziselwe ukudala, ukuqeqesha, noma ukuthuthukisa imodeli evamile ye-machine-learning noma ye-AI ngaphandle kwesici esicelwe yi-tenant.

Imiphumela esizwa yi-AI ingaba nephutha. I-DynamicMail kufanele ibonise idatha ekhishiwe njengomphumela womsebenzi abasebenzisi abagunyaziwe abangawubuyekeza, bawulungise, bawugunyaze, bawenqabe, noma bawususe ngokwendlela yomkhiqizo.

### Usekelo nokufinyelela kwabantu

Abasebenzi be-DynamicMail, osonkontileka, noma ama-subprocessors akufanele bafunde imilayezo ethile ye-Gmail, okunamathiselwe, umbhalo okhishiwe, noma idatha ye-Gmail esuselwe kukho, ngaphandle uma omunye wale mibandela usebenza:

- umsebenzisi ucele ngokucacile usekelo oludinga ukufinyelela kudatha ethile;
- ukufinyelela kudingeka ukuze kuphenywe ukuphepha, kuvinjelwe ukusetshenziswa kabi, noma kuphendulwe esigamekweni;
- ukufinyelela kudingeka ukuze kuthotshelwe umthetho, inqubo yezomthetho, noma umyalelo obophezelayo we-tenant;
- idatha ihlanganisiwe noma yenziwe yangaziwa emisebenzini yangaphakathi futhi akukho okuqukethwe kwe-Gmail komsebenzisi othile okufundekayo.

Ukufinyelela kokusekela kufanele kube ngegunya elincane elidingekayo, kube nesikhathi esilinganiselwe lapho kungenzeka, futhi kulogwe ukuze kube nokuhlolwa kwe-audit.

Iyinto yokusetshenziswa nokubuyekezwa eyenziwe yalolu limi, hhayi iseluleko sokugcina sezomthetho. Akufanele yethulwe njengokuthi inokuvunywa kwe-Google, ukusayinwa ngumeluleki wangaphandle wezomthetho, noma ukucaciselwa kokusetshenziswa komkhiqizo kwama-restricted scopes ngaphandle kobufakazi obuhlukile bokubuyekezwa.

### Izinkomba

- DynamicMail restricted-scope contract: `Documentation/DynamicMail/LocalizedIntegrations/google-restricted-scope-compliance-contract-2026-06-02.md`
- Google API Services User Data Policy: <https://developers.google.com/terms/api-services-user-data-policy>
- Google Workspace API user data and developer policy: <https://developers.google.com/workspace/workspace-api-user-data-developer-policy>
- Gmail API scopes: <https://developers.google.com/workspace/gmail/api/auth/scopes>
- Google restricted-scope verification guidance: <https://developers.google.com/identity/protocols/oauth2/production-readiness/restricted-scope-verification>

## Imigomo yokufinyelela kudatha ye-Google Drive nge-scope ekhawulelwe

Le migomo ichaza ukufinyelela kwe-Google Drive i-DynamicMail ekucelayo lapho umsebenzisi noma umlawuli we-tenant ogunyaziwe exhuma i-Google Drive emisebenzini yemibhalo ye-tenant.

Ama-identity scopes e-Google Sign-In afana ne-`openid`, `email`, ne-`profile` ahlukile kule mvume yokufinyelela kudatha ye-Google Drive. Ukungena ngemvume nge-Google akusho ukuthi ukufinyelela kwe-Google Drive kwamukelwe.

### Scope eceliwe

I-DynamicMail icela `https://www.googleapis.com/auth/drive` kuphela lapho umsebenzisi noma umlawuli we-tenant ogunyaziwe exhuma i-Google Drive emisebenzini yemibhalo ye-tenant. Lena i-restricted Drive scope ebanzi engavumela i-DynamicMail ukubuka nokuphatha wonke amafayela ku-akhawunti ye-Google Drive exhunywe, kuhlanganise namafayela umsebenzisi anawo, amafayela abiwe nomsebenzisi, amafolda, nokuqukethwe kwe-shared drive okutholakala kuleyo akhawunti.

I-DynamicMail kufanele isebenzise i-Drive scope kuphela emisebenzini yemibhalo ye-Drive edaluliwe, ebonakalayo, futhi ekhethwe yi-tenant.

### Idatha i-DynamicMail engayifinyelela

Lapho i-Google Drive ixhunyiwe, i-DynamicMail ingafinyelela idatha ye-Drive edingekayo ukuze inikeze umsebenzi okhethwe yi-tenant, kuhlanganise nalokhu:

- ama-ID amafayela, amagama, izinhlobo ze-MIME, ama-checksum, usayizi, izitembu zesikhathi, izincazelo, ama-label, izinkomba zamafolda, amafolda angabazali, nenye imethadatha yamafayela;
- imethadatha yamafolda, imethadatha ye-shared drive, nemiphumela yokusesha noma yokulista edingekayo ukuze kutholakale imibhalo ye-tenant;
- okuqukethwe kwamafayela, ama-preview, ama-thumbnail, ama-export, ama-download, ama-upload, nama-file payloads akhiqiziwe noma ahleliwe;
- imethadatha yokwabelana nezimvume lapho kudingeka ukubonisa noma ukuqedela isenzo sefayela le-Drive esibonakalayo;
- ulwazi olufingqiwe lwe-Drive olusezingeni le-akhawunti oludingekayo ukuqinisekisa i-akhawunti exhunywe nesimo sokuxhumeka;
- amakhophi agciniwe noma izicashunwa ezigcinwe ku-cache zamafayela e-Drive angeniswe ku-DynamicMail;
- idatha esuselwe kumafayela e-Drive, njengombhalo we-OCR, izinkambu zemibhalo ezihlaziyiwe, ama-label okuhlukanisa, imiphumela yokukhipha, izifinyezo, izehlakalo ze-audit, namarekhodi emibhalo.

I-DynamicMail akufanele icele, iphequlule, ikopishe, ilande, ishintshe, isuse, noma icubungule ngenye indlela idatha ye-Drive engahlobene nomsebenzi wemibhalo ye-Drive obonakalayo.

### Kungani i-DynamicMail isebenzisa idatha ye-Google Drive

I-DynamicMail isebenzisa idatha ye-Google Drive ukuze inikeze imisebenzi yemibhalo ye-Drive ekhethwe yi-tenant. Izinhloso ezihlosiwe yilezi:

- ukuvumela abasebenzisi abagunyaziwe baxhume i-Drive njengomthombo noma indawo okuyiwa kuyo yemibhalo;
- ukuthola, ukulista, ukungenisa, ukulanda, ukuthekelisa, ukulayisha, noma ukubuyekeza imibhalo yebhizinisi ye-tenant ekhethwe ngendlela yomkhiqizo;
- ukukhipha, ukuhlukanisa, nokuhambisa imibhalo ye-Drive emisebenzini ye-DynamicMail;
- ukubonisa isimo sokuxhuma, sezenzo zamafayela, se-sync, nesokucubungula kubasebenzisi be-tenant abagunyaziwe;
- ukugcina amarekhodi e-audit namalogi okusebenza abonisa ukuthi yisiphi isenzo se-Drive esiceliwe futhi saqedwa;
- ukuxazulula izinkinga, ukuphepha, ukuvimbela ukusetshenziswa kabi, ukuphatha izingxabano, nemisebenzi yokuthobela okusemthethweni evunyelwe izinqubomgomo ezifanele nesivumelwano se-tenant.

I-DynamicMail akufanele ithengise idatha ye-Google Drive, iyisebenzisele ukukhangisa noma i-retargeting, iyidlulisele kuma-data brokers, iyisebenzisele ukubheka abantu, noma iyisebenzisele ukunquma ukufaneleka kwesikweletu noma ukufaneleka kokubolekwa.

### Isaziso nge-Drive scope ebanzi nange-scope encane kakhulu

I-scope ethi `https://www.googleapis.com/auth/drive` ibanzi ngoba ingavumela ukufinyelela kuwo wonke amafayela e-Drive atholakala ku-akhawunti exhunywe. I-DynamicMail isebenzisa le scope ku-Data Rooms workflow esebenzayo lapho abasebenzisi abagunyaziwe be-tenant bevumelanisa amafolda namafayela e-Google Drive akhona akhethiwe, bengenisa noma bedawuniloda okuqukethwe kwe-Drive, belayisha noma bebuyekeza amafayela egumbi emuva ku-Drive, futhi besebenzisa izinguquko zokwabelana noma zezimvume ezicelwe ngumsebenzisi kumafayela e-Drive akhona.

Ama-Drive scopes ancane awanele ku-workflow yamanje: `drive.file` ibingamboza kuphela amafayela adalwe noma avulwe yi-DynamicMail futhi ibingambozi amafolda akhona akhethiwe noma ukungenisa wonke amafayela; `drive.readonly` ibingambozi ukulayisha, ukubuyekeza, ukwabelana noma izinguquko zezimvume; ama-metadata-only scopes afana ne-`drive.metadata.readonly`, appdata noma appfolder awakwazi ukudawuniloda noma ukucubungula okuqukethwe kwamadokhumenti e-tenant noma ukuphatha amafayela akhona akhethiwe. Uma umkhiqizo uklanywa kabusha ku-Google Picker namafayela adalwe noma avulwe yi-app kuphela, i-DynamicMail kufanele yehlise i-scope ngaphambi kokukhishwa kwaleyo workflow eklanywe kabusha.

### Ukugcinwa

I-DynamicMail igcina idatha esuselwe ku-Drive kuphela uma kudingeka ngenxa yomsebenzi obonakalayo we-Drive, izilungiselelo ze-tenant zokugcinwa kwemibhalo, amarekhodi e-audit, ukuphepha, ukuphatha izingxabano, noma ukuthobela okusemthethweni. Ama-OAuth tokens nemethadatha yezenzo ze-Drive kugcinwa kuphela ngesikhathi kudingeka ukuze i-Drive integration exhunywe isebenze noma ukuze kugcinwe amarekhodi e-audit adingekayo.

Okuqukethwe kwamafayela e-Drive, amafayela agcinwe ku-cache, imethadatha, umbhalo we-OCR, izinkambu ezikhishiwe, nedatha yemibhalo esuselwe kukho kufanele kususwe noma kwenziwe kungaziwa lapho kungasadingeki enjongweni edaluliwe, ngaphandle uma isibopho sezomthetho, sokuphepha, se-audit, noma sokugcinwa kwe-tenant sidinga ukuqhubeka nokugcinwa.

### Ukususwa

Umsebenzisi noma umlawuli we-tenant ogunyaziwe angacela ukususwa kwedatha egcinwe ku-cache esuselwe ku-Google, amafayela e-Drive angenisiwe, umbhalo okhishiwe, namarekhodi emibhalo asuselwe kukho. I-DynamicMail kufanele isuse noma yenze kungaziwa idatha eceliwe lapho izilungiselelo ze-tenant zokugcinwa kwemibhalo nomthetho osebenzayo zikuvumela.

Ukususa amarekhodi angenisiwe e-DynamicMail akususi ngempela ifayela lasekuqaleni ku-Google Drive. I-DynamicMail kufanele ishintshe, ihambise, ifake kudoti, noma isuse amafayela e-Drive asekuqaleni kuphela lapho umsebenzisi ogunyaziwe ecela ngokucacile leso senzo se-Drive ngendlela yomkhiqizo ebonakalayo futhi isenzo sivunyelwe inqubomgomo ye-tenant nomthetho osebenzayo.

### Ukuhoxisa nokunqamula uxhumano

I-tenant inganqamula i-Google Drive ku-DynamicMail. Ngemuva kokunqamula uxhumano noma ukuhoxiswa kwemvume yasendaweni, i-DynamicMail kufanele iyeke ukusebenzisa ama-OAuth tokens agciniwe e-Google Drive futhi kufanele iyeke ukufunda, ukubhala, ukulanda, ukulayisha, ukushintsha, noma ukususa amafayela e-Drive engeziwe ku-akhawunti exhunywe.

Umnikazi we-akhawunti ye-Google naye angahoxisa ukugunyazwa kwe-app kuzilungiselelo ze-akhawunti ye-Google. Uma ukugunyazwa kwe-Google kuhoxisiwe, i-DynamicMail kufanele imise ukufinyelela kwe-Drive API lapho ukuvuselelwa kwe-token noma ama-API calls ehluleka, futhi uxhumano kufanele luboniswe njengolunqamukile noma oludinga ukuxhunywa kabusha.

Ukuhoxiswa kwasendaweni akususi ngokuzenzakalelayo imibhalo ye-DynamicMail esivele ingenisiwe. Lawo marekhodi aphathwa ngemithetho yokususwa nokugcinwa engenhla.

### Ukusetshenziswa kwe-AI, OCR, nokukhipha

I-DynamicMail ingasebenzisa i-OCR, parsing, ukuhlukanisa, ukufingqa, nokunye ukucubungula okusizwa yi-AI kokuqukethwe kwamafayela e-Drive nemethadatha, kuphela ukuze inikeze noma ithuthukise umsebenzi obonakalayo wemibhalo ye-Drive ye-tenant. Idatha ye-Drive nedatha esuselwe kuyo akufanele isetshenziselwe ukudala, ukuqeqesha, noma ukuthuthukisa imodeli evamile ye-machine-learning noma ye-AI ngaphandle kwesici esicelwe yi-tenant.

Imiphumela esizwa yi-AI ingaba nephutha. I-DynamicMail kufanele ibonise idatha ekhishiwe njengomphumela womsebenzi abasebenzisi abagunyaziwe abangawubuyekeza, bawulungise, bawugunyaze, bawenqabe, noma bawususe ngokwendlela yomkhiqizo.

### Usekelo nokufinyelela kwabantu

Abasebenzi be-DynamicMail, osonkontileka, noma ama-subprocessors akufanele bafunde amafayela athile e-Drive, umbhalo okhishiwe, imethadatha yamafayela, noma idatha ye-Drive esuselwe kukho, ngaphandle uma omunye wale mibandela usebenza:

- umsebenzisi ucele ngokucacile usekelo oludinga ukufinyelela kudatha ethile;
- ukufinyelela kudingeka ukuze kuphenywe ukuphepha, kuvinjelwe ukusetshenziswa kabi, noma kuphendulwe esigamekweni;
- ukufinyelela kudingeka ukuze kuthotshelwe umthetho, inqubo yezomthetho, noma umyalelo obophezelayo we-tenant;
- idatha ihlanganisiwe noma yenziwe yangaziwa emisebenzini yangaphakathi futhi akukho okuqukethwe kwe-Drive komsebenzisi othile okufundekayo.

Ukufinyelela kokusekela kufanele kube ngegunya elincane elidingekayo, kube nesikhathi esilinganiselwe lapho kungenzeka, futhi kulogwe ukuze kube nokuhlolwa kwe-audit.

Iyinto yokusetshenziswa nokubuyekezwa eyenziwe yalolu limi, hhayi iseluleko sokugcina sezomthetho. Akufanele yethulwe njengokuthi inokuvunywa kwe-Google, ukusayinwa ngumeluleki wangaphandle wezomthetho, noma ukucaciselwa kokusetshenziswa komkhiqizo kwama-restricted scopes ngaphandle kobufakazi obuhlukile bokubuyekezwa.

### Izinkomba

- DynamicMail restricted-scope contract: `Documentation/DynamicMail/LocalizedIntegrations/google-restricted-scope-compliance-contract-2026-06-02.md`
- Google API Services User Data Policy: <https://developers.google.com/terms/api-services-user-data-policy>
- Google Workspace API user data and developer policy: <https://developers.google.com/workspace/workspace-api-user-data-developer-policy>
- Google Drive API scopes: <https://developers.google.com/workspace/drive/api/guides/api-specific-auth>
- Google restricted-scope verification guidance: <https://developers.google.com/identity/protocols/oauth2/production-readiness/restricted-scope-verification>
