Home/ Questions/Q 7827897
In Process

The Archive Base Latest Questions

Editorial Team
  • 0
Asked: 2026-06-02T10:05:13+00:00

We have a Salesforce app where we have some custom objects and want to

  • 0

We have a Salesforce app where we have some custom objects and want to expose the various custom object rcords to customers.

We need to ensure that customers can see only the records belonging to their Account. Because of the way these records are setup(owned by various system users at different levels of processing), we cannot use owner based sharing…and cannot use criteria based sharing since its not dynamic(I cant use criteria based sharing to say “Share this record with all customer portal users who belong to the same Account as the record” at runtime).

So I know I have to use Apex based sharing. I have read up on the sharing objects and the sharing table. But how would I approach this.

I can write a trigger which upon inserting will create a share object and get all userids who belong to the customer portal group and whose account equals the account of the record and associate them with the share object of the record.

But I feel this is overkill correct? Lets say there are 5 users from one of our customers and lets say there are 500 records created a day…that means 2500 share objects a day just for 1 customer…for 10 customers this can go upto 25000…and scale in this way…

Am I right here?

Another problem would be if a new person joined that customer team..unless another process updates the sharing on older records, he/she cannot see the older records.

So is there a better/elegant way to do this? I thought of adding a share object to the group…but there is just one group “Customer portal group” and how do I associate the group with the account of the users?

I will appreciate any thoughts about this.

Share

Leave an answer

You must login to add an answer.

Need An Account,

1 Answer

  1. Editorial Team

    You should take a look at high-volume customer portal users. They’re much cheaper relative to standard customer portal users and should meet your needs. Unlike regular users they have a totally different sharing concept. In a nutshell if they own an object they can see, if not they can’t. You can then extend this based on whether a contact or account lookup on the object matches the logged in user.

    Read up on this documentation:

    • 0