You're question isn't really clear. SELinux affects file access, so it can affect sshd's functionality. However, it's not specific to sshd, it can affect any file access on the system, so it affects all applications and users. It's an OS feature.
SELinux is a security feature. You can see if it's enabled using sestatus. For example (bold added by me):
Code:
> sestatus
SELinux status: enabled
SELinuxfs mount: /sys/fs/selinux
SELinux root directory: /etc/selinux
Loaded policy name: targeted
Current mode: enforcing
Mode from config file: enforcing
Policy MLS status: enabled
Policy deny_unknown status: allowed
Max kernel policy version: 31
On this system, it's enabled and enforcing. Because of that, file access is affected not only by the permissions on files/directories, but also the SELinux context, which can create issues because permissions may look fine, but access still gets denied.