Skip to content

Anonymous

My feedback

6 results found

  1. 2 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    Anonymous shared this idea  · 
  2. 3 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    An error occurred while saving the comment
    Anonymous commented  · 

    Is this the same as https://pulse.box.com/forums/909778-help-shape-the-future-of-box/suggestions/41858617-salesforce-integration-default-permissions?

    Reposting my comment from that idea:

    Currently as per https://support.box.com/hc/en-us/articles/360044194673-Box-for-Salesforce-FAQ, ''The user's Box permissions are determined by permissions in Salesforce".

    And even without sync'ing permissions, the user automatically (implicitly) gets Editor permissions from the Account folder (as an example) that cascade down when the user accesses Box from SF.

    We would like to have different levels of permissions (or collaborations) between SF and Box e.g. a user may have read/edit access on Sf but may need to be restricted to only Upload documents to the Account folder (or sub-folder). That is a current business requirement. That is not possible at this point. We should be able to set a different set of collaborations for the user in Box and the SF integration (or plug-in) should enforce that.

    Even when we set the Box user to Uploader manually (or say via Relay workflow), when the user logs in via SF, they are upgraded to 'Editor'.

    Would be interested to know how to 'customize the interaction'

    Anonymous supported this idea  · 
  3. 3 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    Anonymous supported this idea  · 
  4. 4 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    An error occurred while saving the comment
    Anonymous commented  · 

    Currently as per https://support.box.com/hc/en-us/articles/360044194673-Box-for-Salesforce-FAQ, ''The user's Box permissions are determined by permissions in Salesforce".

    And even without sync'ing permissions, the user automatically (implicitly) gets Editor permissions from the Account folder (as an example) that cascade down when the user accesses Box from SF.

    We would like to have different levels of permissions (or collaborations) between SF and Box e.g. a user may have read/edit access on Sf but may need to be restricted to only Upload documents to the Account folder (or sub-folder). That is a current business requirement. That is not possible at this point. We should be able to set a different set of collaborations for the user in Box and the SF integration (or plug-in) should enforce that.

    Even when we set the Box user to Uploader manually (or say via Relay workflow), when the user logs in via SF, they are upgraded to 'Editor'.

    Anonymous supported this idea  · 
  5. 32 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    An error occurred while saving the comment
    Anonymous commented  · 

    Can we please have consistency across the product in adding collaborators? Appears to be a significant gap not allowing a group to be added via Box Relay workflow outcomes

    Anonymous supported this idea  · 
  6. 1 vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    Anonymous shared this idea  · 

Feedback and Knowledge Base