OMGeeky/google-apis-rs
1
0
Fork 0
mirror of https://github.com/OMGeeky/google-apis-rs.git synced 2026-02-23 15:49:49 +01:00
Code Issues Packages Projects Releases Wiki Activity

Update documentation

Browse Source
This commit is contained in:
Sebastian Thiel
2022-03-08 15:36:16 +08:00
parent b84384c010
commit a20241b241
10471 changed files with 1934132 additions and 64947 deletions
Download Patch File Download Diff File Expand all files Collapse all files

14
google_androidenterprise1_cli/users_update/index.html
View File

@@ -5,7 +5,7 @@
<meta charset="utf-8">
<meta name="viewport" content="width=device-width, initial-scale=1.0">
<title>Update - Android Enterprise v2.0.4+20210324</title>
<title>Update - Android Enterprise v3.0.0+20220303</title>
@@ -34,7 +34,7 @@
<nav data-toggle="wy-nav-shift" class="wy-nav-side stickynav">
<div class="wy-side-nav-search">
<a href=".." class="icon icon-home"> Android Enterprise v2.0.4+20210324</a>
<a href=".." class="icon icon-home"> Android Enterprise v3.0.0+20220303</a>
</div>
@@ -598,19 +598,19 @@ In the latter case it is advised to set the field-cursor to the data-structure's
<p>can be set completely with the following arguments which are assumed to be executed in the given order. Note how the cursor position is adjusted to the respective structures, allowing simple field names to be used most of the time.</p>
<ul>
<li><code>-r . account-identifier=sadipscing</code><ul>
<li><code>-r . account-identifier=stet</code><ul>
<li>A unique identifier you create for this user, such as &#34;user342&#34; or &#34;asset#44418&#34;. Do not use personally identifiable information (PII) for this property. Must always be set for EMM-managed users. Not set for Google-managed users.</li>
</ul>
</li>
<li><code>account-type=stet</code><ul>
<li><code>account-type=dolor</code><ul>
<li>The type of account that this user represents. A userAccount can be installed on multiple devices, but a deviceAccount is specific to a single device. An EMM-managed user (emmManaged) can be either type (userAccount, deviceAccount), but a Google-managed user (googleManaged) is always a userAccount.</li>
</ul>
</li>
<li><code>display-name=dolor</code><ul>
<li><code>display-name=duo</code><ul>
<li>The name that will appear in user interfaces. Setting this property is optional when creating EMM-managed users. If you do set this property, use something generic about the organization (such as &#34;Example, Inc.&#34;) or your name (as EMM). Not used for Google-managed user accounts. @mutable androidenterprise.users.update</li>
</ul>
</li>
<li><code>id=duo</code><ul>
<li><code>id=vero</code><ul>
<li>The unique ID for the user.</li>
</ul>
</li>
@@ -618,7 +618,7 @@ In the latter case it is advised to set the field-cursor to the data-structure's
<li>The entity that manages the user. With googleManaged users, the source of truth is Google so EMMs have to make sure a Google Account exists for the user. With emmManaged users, the EMM is in charge.</li>
</ul>
</li>
<li><code>primary-email=vero</code><ul>
<li><code>primary-email=invidunt</code><ul>
<li>The user&#39;s primary email address, for example, &#34;jsmith@example.com&#34;. Will always be set for Google managed users and not set for EMM managed users.</li>
</ul>
</li>