签约开发者能否安装Filemaker Pro 16并使用客户现有账号登录开发？
Great question—let’s break this down from licensing, security, and practicality angles since I’ve dealt with similar scenarios before.
Licensing is the first big concern
FileMaker Pro 16 licenses are typically tied to a specific user or device (depending on the license type your client has). Installing their licensed copy on your own machine and using their login credentials likely violates FileMaker’s end-user license agreement (EULA). You’ll want to double-check the exact terms with your client’s license documentation, but most standard licenses don’t allow sharing the software or login with third-party developers for commercial work.Security and accountability risks can’t be ignored
Using your client’s personal login gives you full access to their live database data—any accidental edits, deletions, or data exposure could lead to serious consequences for both you and the client. Plus, if the client changes their password, revokes access, or their account has issues, your development workflow gets immediately disrupted. It’s never a good idea to rely on someone else’s primary account for your work.Better, more compliant workarounds
If you want the convenience of using FileMaker Pro instead of only the API, here are safer options:- Ask your client to set up a restricted, dedicated development account in their FileMaker database—limit its permissions only to the modules and data you need to work on, so you don’t have full access to sensitive information.
- Use FileMaker’s free trial version (or a developer license if you have one) on your own machine, and have the client share a clone of their database (with test data) for you to work with locally. This lets you use the full FileMaker Pro interface without touching their live system or violating licensing rules.
- If the client can share a test instance of their database server, you can connect your own FileMaker Pro installation to that test environment with your dedicated dev account.
At the end of the day, skipping these steps to save a little time isn’t worth the legal or security risks. Taking the extra minute to set up a compliant development environment will keep both you and your client protected.
内容的提问来源于stack exchange，提问作者Dane Iracleous
