Note that there are some explanatory texts on larger screens.

plurals
  1. POSurpress notification for google documents permission additions when using API
    primarykey
    data
    text
    singulars
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    plurals
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. COIf you have a reproducible case, perhaps follow up w/ original google ticket: Perhaps follow up on original ticket http://code.google.com/a/google.com/p/apps-api-issues/issues/detail?id=2382
      singulars
    2. COWhat do you mean by Creating an ACL? I have not used this API so I have no first-hand experience in this; but from a quick look at the documentation that you provided link for, what I understand is that you do not create an ACL, you create a document and it has an ACL that lists you as the owner. Then, when you want to add the other user whom you do not want to send e-mails, what you do is to UPDATE the ACL. You add the parameter to this request and the other user never gets an e-mail about his being added to this document as viewer.
      singulars
    3. COI "think" I'm reading it correctly, right??. Here is the applicable text: "Creating an ACL entry that shares a document or collection with users will by default notify relevant users via email that they have new access to the document or collection. However, these emails can be disabled by attaching the send-notification-emails parameter to ACL URIs when modifying an ACL.". To me this is saying (and in my testing I have proved this) that if you are adding someone via creating ACL then they will always get notified, but on an update of their ACL you have the option.
      singulars
 

Querying!

 
Guidance

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload