A foreign key is a database column that must match a value in another table, and it is used to link related records. For example, an order record may hold a customer identifier that must exist in the customers table, so the database refuses an order for a customer that does not exist.
It matters for data integrity, because it keeps relationships consistent. In multi-tenant designs, it can also play a part in security, for instance by making sure that records belong to the same tenant as the records they refer to.
It does not by itself enforce who may see what. A foreign key checks that a value exists and not that the current user is allowed to access it, and the way the database reports violations can reveal information, because an error message may show whether a record exists. How foreign keys behave, for example when a linked record is deleted, depends on how they are defined.
When designing a schema, define foreign keys for important relationships, include the tenant in them where it matters and make sure error messages do not give away more than they should.