Using Attribute-Based Encryption (ABE) the sender does not need to specify the identity of the recipient when encrypting. Instead, the sender specifies attributes of the recipient that will enable any one entity possessing those attributes to decrypt the message, while preventing anyone not possessing all of those attributes from decrypting it.

An example could be a CEO encrypting a message to be read only by managers in the sales area. He does not want it read by the cashiers in sales, nor by managers in the HR or shipping departments. He would encrypt it using the attributes of {"manager", "sales"}. Only users with both of those attributes would have enough information to decrypt the message.

Extending the above example, an HR manager might have the attributes {"manager", "HR"}, while a cashier would have the attributes {"cashier", "sales"}. Those two people could try to combine their attributes to include "manager" and "sales", and then attempt to decrypt the message together. ABE schemes prevent this type of collusion.