How to read/write specific data on Firestore
I'm having some problem with the READ rules
of Firestore currently
Here is my data structure
email: example@gmail.com,
username: geekGi3L,
birthday: 1995/02/14,
photo: <firestore-download-url>
The rules
currently I set is
service cloud.firestore
match /databases/database/documents
match /users/user
allow read;
allow write: if request.auth.uid != null && request.auth.uid == user;
How could I set the rules
to allow user to READ the specific fields like email
and birthday
only if request.auth.uid != null && request.auth.uid == uid
while username
and photo
should be readable by every user?
Thank you <3
google-cloud-firestore firebase-security-rules
add a comment |
I'm having some problem with the READ rules
of Firestore currently
Here is my data structure
email: example@gmail.com,
username: geekGi3L,
birthday: 1995/02/14,
photo: <firestore-download-url>
The rules
currently I set is
service cloud.firestore
match /databases/database/documents
match /users/user
allow read;
allow write: if request.auth.uid != null && request.auth.uid == user;
How could I set the rules
to allow user to READ the specific fields like email
and birthday
only if request.auth.uid != null && request.auth.uid == uid
while username
and photo
should be readable by every user?
Thank you <3
google-cloud-firestore firebase-security-rules
add a comment |
I'm having some problem with the READ rules
of Firestore currently
Here is my data structure
email: example@gmail.com,
username: geekGi3L,
birthday: 1995/02/14,
photo: <firestore-download-url>
The rules
currently I set is
service cloud.firestore
match /databases/database/documents
match /users/user
allow read;
allow write: if request.auth.uid != null && request.auth.uid == user;
How could I set the rules
to allow user to READ the specific fields like email
and birthday
only if request.auth.uid != null && request.auth.uid == uid
while username
and photo
should be readable by every user?
Thank you <3
google-cloud-firestore firebase-security-rules
I'm having some problem with the READ rules
of Firestore currently
Here is my data structure
email: example@gmail.com,
username: geekGi3L,
birthday: 1995/02/14,
photo: <firestore-download-url>
The rules
currently I set is
service cloud.firestore
match /databases/database/documents
match /users/user
allow read;
allow write: if request.auth.uid != null && request.auth.uid == user;
How could I set the rules
to allow user to READ the specific fields like email
and birthday
only if request.auth.uid != null && request.auth.uid == uid
while username
and photo
should be readable by every user?
Thank you <3
google-cloud-firestore firebase-security-rules
google-cloud-firestore firebase-security-rules
asked Nov 10 at 4:43
Felicia
304
304
add a comment |
add a comment |
1 Answer
1
active
oldest
votes
In Firstore, there is no per-field access control for reading fields of a document. The most granular unit of access is the document. A user either has full access to read a document in its entirety, or they don't have any access at all.
If you need to change access per field, you'll have to split the fields of the document into multiple collections, with each collection having access control appropriate for the fields of the documents within. It's very common to have a split between public and private data like this.
Oh I see... noted thank you for saving my day ;)
– Felicia
Nov 10 at 8:29
add a comment |
Your Answer
StackExchange.ifUsing("editor", function ()
StackExchange.using("externalEditor", function ()
StackExchange.using("snippets", function ()
StackExchange.snippets.init();
);
);
, "code-snippets");
StackExchange.ready(function()
var channelOptions =
tags: "".split(" "),
id: "1"
;
initTagRenderer("".split(" "), "".split(" "), channelOptions);
StackExchange.using("externalEditor", function()
// Have to fire editor after snippets, if snippets enabled
if (StackExchange.settings.snippets.snippetsEnabled)
StackExchange.using("snippets", function()
createEditor();
);
else
createEditor();
);
function createEditor()
StackExchange.prepareEditor(
heartbeatType: 'answer',
autoActivateHeartbeat: false,
convertImagesToLinks: true,
noModals: true,
showLowRepImageUploadWarning: true,
reputationToPostImages: 10,
bindNavPrevention: true,
postfix: "",
imageUploader:
brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
allowUrls: true
,
onDemand: true,
discardSelector: ".discard-answer"
,immediatelyShowMarkdownHelp:true
);
);
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function ()
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f53236052%2fhow-to-read-write-specific-data-on-firestore%23new-answer', 'question_page');
);
Post as a guest
Required, but never shown
1 Answer
1
active
oldest
votes
1 Answer
1
active
oldest
votes
active
oldest
votes
active
oldest
votes
In Firstore, there is no per-field access control for reading fields of a document. The most granular unit of access is the document. A user either has full access to read a document in its entirety, or they don't have any access at all.
If you need to change access per field, you'll have to split the fields of the document into multiple collections, with each collection having access control appropriate for the fields of the documents within. It's very common to have a split between public and private data like this.
Oh I see... noted thank you for saving my day ;)
– Felicia
Nov 10 at 8:29
add a comment |
In Firstore, there is no per-field access control for reading fields of a document. The most granular unit of access is the document. A user either has full access to read a document in its entirety, or they don't have any access at all.
If you need to change access per field, you'll have to split the fields of the document into multiple collections, with each collection having access control appropriate for the fields of the documents within. It's very common to have a split between public and private data like this.
Oh I see... noted thank you for saving my day ;)
– Felicia
Nov 10 at 8:29
add a comment |
In Firstore, there is no per-field access control for reading fields of a document. The most granular unit of access is the document. A user either has full access to read a document in its entirety, or they don't have any access at all.
If you need to change access per field, you'll have to split the fields of the document into multiple collections, with each collection having access control appropriate for the fields of the documents within. It's very common to have a split between public and private data like this.
In Firstore, there is no per-field access control for reading fields of a document. The most granular unit of access is the document. A user either has full access to read a document in its entirety, or they don't have any access at all.
If you need to change access per field, you'll have to split the fields of the document into multiple collections, with each collection having access control appropriate for the fields of the documents within. It's very common to have a split between public and private data like this.
answered Nov 10 at 5:17
Doug Stevenson
70.2k880101
70.2k880101
Oh I see... noted thank you for saving my day ;)
– Felicia
Nov 10 at 8:29
add a comment |
Oh I see... noted thank you for saving my day ;)
– Felicia
Nov 10 at 8:29
Oh I see... noted thank you for saving my day ;)
– Felicia
Nov 10 at 8:29
Oh I see... noted thank you for saving my day ;)
– Felicia
Nov 10 at 8:29
add a comment |
Thanks for contributing an answer to Stack Overflow!
- Please be sure to answer the question. Provide details and share your research!
But avoid …
- Asking for help, clarification, or responding to other answers.
- Making statements based on opinion; back them up with references or personal experience.
To learn more, see our tips on writing great answers.
Some of your past answers have not been well-received, and you're in danger of being blocked from answering.
Please pay close attention to the following guidance:
- Please be sure to answer the question. Provide details and share your research!
But avoid …
- Asking for help, clarification, or responding to other answers.
- Making statements based on opinion; back them up with references or personal experience.
To learn more, see our tips on writing great answers.
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function ()
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f53236052%2fhow-to-read-write-specific-data-on-firestore%23new-answer', 'question_page');
);
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown